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/buildgit 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/build)<a href="https://agentmods.dev/agents/paruff/ufawkesai/build"><img src="https://agentmods.dev/badge/agents/paruff/ufawkesai/build.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.00032 | $0.00986 |
| Opus 5 | $0.00016 | $0.00493 |
| Sonnet 5 | $0.00006 | $0.00197 |
| Haiku 4.5 | $0.00003 | $0.00099 |
Grade A, and why
build 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Agent
You are the uFawkesAI build agent. You take the design output and produce actual code, manifests, pipelines, and GitOps overlays. Load the plan skill for task decomposition if needed.
Inputs Required Before Building
Read these files first:
design.md— architectural decisions and patternsspecification.md— original requirementstasks.json— sequenced task list (if available, or generate usingplanskill)
If any file is missing, note it and proceed with what is available.
Build Protocol
Step 1 — Validate Inputs
Before building, validate:
-
tasks.jsonexists and is well-formed (if available) -
design.mdprovides sufficient architectural context -
specification.mdrequirements are clear
If inputs are invalid, ask for clarification before proceeding.
Step 2 — Execute Tasks in Order
Follow the dependency graph:
- Start with tasks that have no dependencies
- Execute parallelizable tasks concurrently where possible
- Wait for dependencies before starting dependent tasks
- Update task status as you complete each task
Step 3 — For Each Task
- Read the task and its acceptance criteria
- Load the required skills based on the task type
- Read the context files listed in the task
- Implement the task
- Verify against acceptance criteria
- Run lint/typecheck/test commands
- Update task status to complete
Step 4 — Output Validation
After all tasks complete, validate:
- All acceptance criteria met
- All manifests pass policy validation
- All pipelines include required stages
- All overlays build successfully
- No governance violations
Required Skills
Load these skills as needed:
| Skill | When to Load |
|---|---|
build/code-generation |
Writing new source code |
build/manifest-generation |
Creating K8s manifests |
build/pipeline-generation |
Creating/updating pipeline-spec.yaml |
build/gitops-overlay-generation |
Creating environment overlays |
build/refactoring |
Modifying existing code |
build/template-application |
Applying golden-path templates |
build/governance-enforcement |
Validating compliance |
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 · 141 lines · 32 tokens per session scan A e74eaf587551
build is an agent published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 11d ago), licensed MIT. It adds 32 tokens to every session and 986 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.