graph-security

Estrelas6

Forks3

Atualizado24 de julho de 2026 às 00:01

Security audit via the `agf` CLI — OWASP / STRIDE / secrets. Run when a change touches authn/authz, external I/O, or secrets, as a gate parallel to harness, or before deploying sensitive features.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

DiegoNogueiraDev

DiegoNogueiraDev/agf

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de segurança da informaçãoInformática e Matemática·SOC 15-1212

SKILL.md

readonly

name	graph-security
description	Security audit via the `agf` CLI — OWASP / STRIDE / secrets. Run when a change touches authn/authz, external I/O, or secrets, as a gate parallel to harness, or before deploying sensitive features.
triggers	["graph-security"]
version	2.0.0
author	auto-generated
date	"2026-06-16T00:00:00.000Z"
category	REVIEW
phase	REVIEW
tokens	~578
phases	["REVIEW","DEPLOY"]

graph-security

Security audit (OWASP / STRIDE / secrets). Drive via the agf CLI — zero MCP. Load context with agf context <id> first.

When to Use

Change touches authn/authz, external I/O, or secrets
Gate parallel to harness
Before deploying sensitive features

Mandatory Flow

agf check <id> → agf scan-repos → agf node add --type risk

Steps

REVIEW-phase agf commands:

Command	What it does
`agf check <id>`	Includes the per-task security gate
`agf harness`	Agent-readiness (parallel to security)
`agf node add --type risk`	Track security findings as a risk node
`agf scan-repos`	Scan neighbor repos for known vulns

Workflow

Per-Task Check — agf check <id> (per-task security gate)
Repo Scan — agf scan-repos (npm audit, secrets grep, Zod boundaries)
STRIDE Analysis — threats per category (Spoofing, Tampering, Repudiation, Info Disclosure, DoS, Elevation)
Register Findings — agf node add --type risk
Mitigate — create tasks to fix critical/high findings
Validate — no critical secret/vuln remaining

Exit

No critical secret/vuln
Findings tracked as risk nodes
Security gate pass

Anti-Patterns

Don't ignore findings — always track as risk nodes
Don't assume harness covers security — they're parallel gates
Don't deploy with critical vulns — fix before DEPLOY
Don't skip neighbor-repo scan — supply chain matters

Output Format

Phase: SECURITY (REVIEW parallel)
Findings: N risks (K critical, M high, J medium)
Secrets: scan result
Vulns: npm audit result
STRIDE: categories covered
Gate: security pass/fail
Status: Security gate passed

Loop Link

Parallel to REVIEW → DEPLOY. After tasks, agf savings / agf metrics --economy-report → agf learning → calibrate next turn.

Related Skills

$graph-review — agf skill show graph-review
$graph-deploy — agf skill show graph-deploy

Codex Notes

In Codex Plan Mode, plan only — do not mutate files.
During implementation, follow AGENTS.md and use apply_patch for manual edits.

Token Economy

Economia de tokens. Os levers compartilhados por todas as skills — --select, agf retrieve-command, agf exec chain, reuso antes de criação — vivem em _shared.md → Token Economy. Fonte única: um parágrafo repetido em trinta arquivos é o trigésimo primeiro que envelhece sozinho.

Mais deste repositório

mesmo repositório

graph-accessibility

DiegoNogueiraDev/agf

Accessibility compliance audit using WCAG 2.2 AA standards, ARIA validation, screen reader testing, keyboard navigation, color contrast analysis, and i18n readiness

2026-07-246

graph-analyze

DiegoNogueiraDev/agf

Execute the ANALYZE phase of the lifecycle via the `agf` CLI — PRD creation, requirements, Definition of Ready (7 checks), cross-project learning

2026-07-246

graph-api-design

DiegoNogueiraDev/agf

API governance and design audit using OpenAPI/Swagger spec generation, REST maturity model, contract validation, and breaking change detection

2026-07-246

graph-architecture

DiegoNogueiraDev/agf

Architecture governance using C4 Model, ADR lifecycle, Architecture Fitness Functions, layer boundary enforcement, and drift detection

2026-07-246

graph-backlog-generation

DiegoNogueiraDev/agf

Human-in-the-loop PLANNING skill — investigates the project (graph + git + harness/gaps) and runs the whole ANALYZE→DESIGN→PLAN chain in one faceted loop to produce a COMPLETE PRD injected as graph backlog (epics, tasks, testable AC) for a separate agent to implement. Applies the project's planning methodologies — Impact Mapping + OKR per epic, JTBD, MoSCoW, WSJF/Cost-of-Delay, User Story Mapping, Example Mapping (Rules/Examples → Given-When-Then AC), SPIDR splitting, INVEST, Definition of Ready, Risk Matrix; the full catalogue lives in the skill body. Stops for the human after each complete PRD and iterates the next cycle from the project's own findings (dogfood). Does NOT implement. Triggers — graph-backlog-generation, gerar backlog, criar PRD, planejar feature, detalhar épico, novo ciclo, "plan the next thing", "what should we build next".

2026-07-246

graph-bug-hunter

DiegoNogueiraDev/agf

Automated bug discovery through static analysis, LSP diagnostics, pattern detection, regression hotspot analysis, and error catalog mining

2026-07-246

name	graph-security
description	Security audit via the `agf` CLI — OWASP / STRIDE / secrets. Run when a change touches authn/authz, external I/O, or secrets, as a gate parallel to harness, or before deploying sensitive features.
triggers	["graph-security"]
version	2.0.0
author	auto-generated
date	"2026-06-16T00:00:00.000Z"
category	REVIEW
phase	REVIEW
tokens	~578
phases	["REVIEW","DEPLOY"]

graph-security

Security audit (OWASP / STRIDE / secrets). Drive via the agf CLI — zero MCP. Load context with agf context <id> first.

When to Use

Change touches authn/authz, external I/O, or secrets
Gate parallel to harness
Before deploying sensitive features

Mandatory Flow

agf check <id> → agf scan-repos → agf node add --type risk

Steps

REVIEW-phase agf commands:

Command	What it does
`agf check <id>`	Includes the per-task security gate
`agf harness`	Agent-readiness (parallel to security)
`agf node add --type risk`	Track security findings as a risk node
`agf scan-repos`	Scan neighbor repos for known vulns

Workflow

Per-Task Check — agf check <id> (per-task security gate)
Repo Scan — agf scan-repos (npm audit, secrets grep, Zod boundaries)
STRIDE Analysis — threats per category (Spoofing, Tampering, Repudiation, Info Disclosure, DoS, Elevation)
Register Findings — agf node add --type risk
Mitigate — create tasks to fix critical/high findings
Validate — no critical secret/vuln remaining

Exit

No critical secret/vuln
Findings tracked as risk nodes
Security gate pass

Anti-Patterns

Don't ignore findings — always track as risk nodes
Don't assume harness covers security — they're parallel gates
Don't deploy with critical vulns — fix before DEPLOY
Don't skip neighbor-repo scan — supply chain matters

Output Format

Phase: SECURITY (REVIEW parallel)
Findings: N risks (K critical, M high, J medium)
Secrets: scan result
Vulns: npm audit result
STRIDE: categories covered
Gate: security pass/fail
Status: Security gate passed

Loop Link

Parallel to REVIEW → DEPLOY. After tasks, agf savings / agf metrics --economy-report → agf learning → calibrate next turn.

Related Skills

$graph-review — agf skill show graph-review
$graph-deploy — agf skill show graph-deploy

Codex Notes

In Codex Plan Mode, plan only — do not mutate files.
During implementation, follow AGENTS.md and use apply_patch for manual edits.

Token Economy

Economia de tokens. Os levers compartilhados por todas as skills — --select, agf retrieve-command, agf exec chain, reuso antes de criação — vivem em _shared.md → Token Economy. Fonte única: um parágrafo repetido em trinta arquivos é o trigésimo primeiro que envelhece sozinho.