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 skills/cofin/flow/architecture-criticnpx skills add cofin/flow --skill architecture-criticgit clone --depth 1 https://github.com/cofin/flowWrote 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/skills/cofin/flow/architecture-critic)<a href="https://agentmods.dev/skills/cofin/flow/architecture-critic"><img src="https://agentmods.dev/badge/skills/cofin/flow/architecture-critic.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.1 | $0.00039 | $0.00324 |
| Opus 5 | $0.00019 | $0.00162 |
| Sonnet 5 | $0.00008 | $0.00065 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
architecture-critic 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 6d 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.
What it actually says
Architecture Critic
Review structural decisions for practical maintainability over the next 6-12 months. Use directly or as a subagent in planning and design review.
Workflow
- Load the persona and architecture checklist below.
- Inspect the concrete design, code, and change boundaries.
- Apply every relevant architecture axis and report only evidence-backed strengths or concerns.
Guardrails
Follow the persona boundaries. Do not invent future requirements or recommend abstractions without a demonstrated structural need.
Output
For each concern, report the structural problem, long-term consequence, and recommendation. If the architecture is appropriately simple, explain why it holds up.
Validation
Confirm findings are structural, evidence-backed, and proportional to the 6-12 month horizon.
Example
Report a service's direct dependency on another component's storage schema as a coupling concern, including its blast radius and a stable boundary fix.
References
- Persona — role, horizon, approach, and boundaries.
- Architecture checklist — review axes and evidence checks.
- Stances — optional multi-view prompts.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 60 lines · 39 tokens per session scan A cdc2cf46defc
architecture-critic is a skill published in the GitHub repository cofin/flow (16 stars, last pushed 7d ago), licensed Apache-2.0. It adds 39 tokens to every session and 324 once invoked, about $0.0002 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-30.
Other skills, from other repositories
write-documentation
Use when writing or substantially rewriting human-facing prose: documentation, README, guides, blog posts, emails, Slack messages, PR descriptions, release notes, or any text a human will read. Not for code comments, commit messages, or agent-to-agent communication.
document-release
Use when implementation on a branch is complete and it is about to be merged or PR'd — or when finishing-a-development-branch reaches its docs-audit gate — and after code changes are committed, to ensure all project documentation accurately reflects shipped code. Covers README, ARCHITECTURE, CONTRIBUTING, CHANGELOG…
stress-test
Use when a design, plan, or decision needs adversarial scrutiny before proceeding. Interrogates every branch of the decision tree, providing recommended answers and forcing explicit agreement or pushback. Triggers on "grill me", "stress test this", "poke holes", "challenge this design", or when…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification.
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code.