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.
git 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/architecture-review)<a href="https://agentmods.dev/commands/alifanov/darkflow/architecture-review"><img src="https://agentmods.dev/badge/commands/alifanov/darkflow/architecture-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/alifanov/darkflow/architecture-review"><img src="https://agentmods.dev/badge/commands/alifanov/darkflow/architecture-review.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00023 | $0.01659 |
| Opus 5 | $0.00012 | $0.00830 |
| Sonnet 5 | $0.00005 | $0.00332 |
| Haiku 4.5 | $0.00002 | $0.00166 |
Grade A, and why
architecture-review 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 8d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly structural pass, in two parts. The review reads the codebase for module boundaries, coupling and layering — it works on any language. The fallow step adds deterministic TS/JS findings (dead code, duplication, cycles, complexity) on top; it is optional precisely because it only covers TS/JS while the rest of the review does not.
Proposal-only. It identifies problems and files tasks. It changes nothing itself — that is
a human / fix-issues decision.
Step 1 — Read project config
Load the project config (contract in .darkflow.d/claude.md → Project config). Uses: language.
Step 2 — Architecture review
/improve-codebase-architecture
Step 3 — Code health (TS/JS only — skip otherwise)
Skip this step unless the project is TypeScript/JavaScript (package.json plus tsconfig.json
or .ts/.tsx/.js files). A Python or Go repo goes straight to Step 4 with the review's
findings alone — that is a normal outcome, not a degraded run, and it needs no note anywhere.
The fallow skill (~/.claude/skills/fallow) teaches the exact commands, flags, JSON shape
and gotchas — follow it. The entry point is the aggregated audit:
npx fallow audit --json
If npx fallow is unavailable, cargo install fallow-cli once, or skip the step. Never guess
findings — this half is only worth running while it stays deterministic.
Collect at minimum: dead code (unused exports, files, unreachable code) · duplication · circular dependencies and boundary violations · complexity hotspots · dependency hygiene.
Read the actions array; each finding carries an auto_fixable flag. auto_fixable does not
mean "safe to delete" — that judgement is Step 4.
Step 4 — Triage (never trust the tool blindly)
fallow is deterministic but context-blind, and the review can over-reach. Filter first:
- Dead code that is actually live: public API surface (
exports/main/types), framework entry points (page.tsx,route.ts,layout.tsx,app/**,pages/**), dynamically referenced symbols (string-keyed lookups, DI, reflection), test fixtures, generated files, type-only re-exports consumed downstream. The skill's gotchas reference has the full list. - Duplication that is intentional: generated code, vendored snapshots, deliberately decoupled copies. Propose extraction only when the blocks are genuinely the same concern.
- Complexity that is inherent: a parser or a state machine is legitimately complex. Propose a
refactor only where the complexity is accidental and the file changes often (cross-check
git logchurn). - Style preferences are not findings. Actionable structural problems only.
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.
- 8d ago First seen · 175 lines · 23 tokens per session scan A c37195473f8d
architecture-review is a command published in the GitHub repository alifanov/darkflow (3 stars, last pushed 9d ago), licensed MIT. It adds 23 tokens to every session and 1,659 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
maintainer-review-error-handling
Review the PR for error-handling correctness — surfaced errors, no silent swallows, consistent error patterns (Pi-tuned).
afr
Review feature - code review with fixes by a different agent (shortcut for feature-code-review).
simplify-analyze
Analyze code for simplification opportunities. Part of simplify- family.
simplify
Orchestrates code simplification via verified transformations. Delegates to simplify-analyze, simplify-verify, and simplify-transform.
dream
Overnight autoresearch + maintainer sweep that surfaces a MORNING REPORT — suggested changes, issues raised with fixes, and kept improvements. Shadow-first; never auto-pushes. Runs on-demand or scheduled for off-hours.
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.