Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/alifanov/darkflow/security-auditgit clone --depth 1 https://github.com/alifanov/darkflowWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/alifanov/darkflow/security-audit)<a href="https://agentmods.dev/commands/alifanov/darkflow/security-audit"><img src="https://agentmods.dev/badge/commands/alifanov/darkflow/security-audit.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00022 | $0.01430 |
| Opus 5 | $0.00011 | $0.00715 |
| Sonnet 5 | $0.00004 | $0.00286 |
| Haiku 4.5 | $0.00002 | $0.00143 |
Grade A, and why
security-audit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly security pass. It covers both halves that used to be separate routines: what GitHub already knows (Dependabot, code scanning, secret scanning) and what only a reading of the code finds. The GitHub half is cheap and runs first — it is also the half that can already have a fix waiting.
The cost of folding the daily vulnerability-check into this weekly run is response time: a
Dependabot advisory can now sit for up to seven days instead of one. Accepted knowingly.
Step 1 — Read project config
Load the project config (contract in .darkflow.d/claude.md → Project config). Uses: language.
Step 2 — GitHub alerts
REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner)
Fetch open alerts from all three surfaces. Any of them may return 404 or 403 when the
feature is off or the token lacks scope — that means "no findings from that surface", not an
error to stop on.
gh api -X GET "/repos/${REPO}/dependabot/alerts" -f state=open --paginate 2>/dev/null || echo "[]"
gh api -X GET "/repos/${REPO}/code-scanning/alerts" -f state=open --paginate 2>/dev/null || echo "[]"
gh api -X GET "/repos/${REPO}/secret-scanning/alerts" -f state=open --paginate 2>/dev/null || echo "[]"
Derive a stable identifier per alert — it is what dedup in Step 4 matches on:
- Dependabot:
security_advisory.ghsa_id+ affected package name and version range - Code scanning:
rule.id+ file path + line - Secret scanning: secret type + the locations array — never the secret value itself
Step 3 — Code review
/security-review
Step 4 — Deduplicate, then file
Read every task in the project, not just this routine's own:
~/.darkflow/df task list --state all --format compact
The same weakness reaches two audits from two directions — a missing rate limit is a security
finding and an architecture one — and filtering by --source would let it land twice. Skip a
finding when it matches an existing task or one a human already closed without a merged fix
(rejected). Re-file only when a previously-fixed problem has demonstrably regressed.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 155 lines · 22 tokens per session scan A 6057af7276b5
security-audit is a command published in the GitHub repository alifanov/darkflow (2 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session and 1,430 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
project
Generate project documentation (product.md, structure.md, tech.md, codemaps/).
toh-help
Display all Toh Framework commands and quick usage guide.
feature
Create a feature specification using spec-driven development.
deep-audit.skeleton
Aciklama: Bu bolum Bootstrap tarafindan manifest verileriyle doldurulur. Gerekli manifest alanlari: project.description, stack.primary, project.structure, project.subprojects, stack.orm, stack.authmethod Ornek cikti.
fix-issue
!gh issue view $ARGUMENTS 2>/dev/null || echo "Could not fetch issue $ARGUMENTS".
rev
Invoke Code Reviewer for code quality, security, requirements validation, and best practices review.