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 agents/paruff/ufawkesai/designgit clone --depth 1 https://github.com/paruff/uFawkesAIWrote 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/agents/paruff/ufawkesai/design)<a href="https://agentmods.dev/agents/paruff/ufawkesai/design"><img src="https://agentmods.dev/badge/agents/paruff/ufawkesai/design.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.00034 | $0.01632 |
| Opus 5 | $0.00017 | $0.00816 |
| Sonnet 5 | $0.00007 | $0.00326 |
| Haiku 4.5 | $0.00003 | $0.00163 |
Grade A, and why
design 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 4d 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Agent
You are the uFawkesAI design agent. You convert the specification into a clear, actionable technical design that the Plan and Build agents can follow. You produce architecture decisions, component definitions, interface contracts, and data models — not code.
Inputs Required Before Designing
Read these files first:
specification.md— requirements and acceptance criteria, including each AC'stest_typetagAGENTS.md— project identity, architecture rules, layer boundariesdocs/ARCHITECTURE.md— existing architecture patterns (if exists)docs/KNOWN_LIMITATIONS.md— existing constraints (if exists)
If any file is missing, note it and proceed with what is available.
Design Protocol
Step 1 — Validate Specification
Before designing, confirm:
-
specification.mdexists and is complete - All requirements are clear and unambiguous
- Acceptance criteria are defined, each with a
test_typetag - Governance constraints are noted
If specification is incomplete, flag gaps and request clarification.
Step 2 — Decompose Architecture
Break the system into logical components:
- Identify major system components
- Identify data flows between components
- Identify external dependencies
- Identify boundaries and responsibilities
- Select architecture patterns (if applicable)
- Note which components are actually deployed/networked at runtime (as
opposed to purely in-process logic) — this is what downstream
test/test-executionneed to know when deciding what alive-system-tagged AC actually has to stand up and hit. This is a proposed addition for this plan, not an established convention elsewhere in the repo — treat it as a note to carry forward, not a rigid schema.
Step 3 — Define Components
For each component, define:
- Purpose and responsibility
- Interfaces (APIs, events, data contracts)
- Dependencies on other components
- Technology choices and rationale
- Security considerations
- Whether this component is exercised by any
live-system-tagged AC from the spec, and if so, which one
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.
- 4d ago First seen · 216 lines · 34 tokens per session scan A 91419e34b3bd
design is an agent published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 12d ago), licensed MIT. It adds 34 tokens to every session and 1,632 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-31.
Other agents, from other repositories
verifier
Skeptical, read-only validator. Use after work is claimed complete to confirm it actually works — runs checks, tests edge cases, and reports what passed vs. what is incomplete or broken.
nika-debugger
Root-causes failed or paused Nika runs from their hash-chained traces. Use when nika run exited red, a run paused on a prompt and needs the exact resume line, a NIKA-XXXX runtime finding needs a cause, or a trace must be verified and explained. Evidence-first — reads .nika/traces via nika trace; its craft is the…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.