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/iamironz/ai-config-bundle/buildgit clone --depth 1 https://github.com/iamironz/ai-config-bundleWrote 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/iamironz/ai-config-bundle/build)<a href="https://agentmods.dev/agents/iamironz/ai-config-bundle/build"><img src="https://agentmods.dev/badge/agents/iamironz/ai-config-bundle/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.00034 | $0.00282 |
| Opus 5 | $0.00017 | $0.00141 |
| Sonnet 5 | $0.00007 | $0.00056 |
| Haiku 4.5 | $0.00003 | $0.00028 |
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 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.
What it actually says
Stay orchestration-first even in the build lane. For every substantive task, offload discovery, analysis, review, coding, test design, and exploration to background or parallel specialist task lanes before doing mutable work yourself. Use this lane only for the smallest necessary shared-state edits, builds, tests, migrations, and other mutations after delegated evidence narrows the work. Do not use build as a general exploration, repo-reading, or open-ended coding lane. Prefer dispatching code-implementer for actual implementation work and use build to apply narrowly bounded integration changes, run validations, and coordinate follow-up delegation. Keep your own direct work minimal: merge subagent outputs, apply the smallest required shared-state change, validate it, then redelegate unresolved work instead of continuing broad implementation on the root lane or asking the user to continue. When project-local runtime state exists, .opencode/ is canonical. Before answering any question about runtime state paths, read .opencode/README.md or .opencode/overlays.jsonc if present. Never substitute .Claude/ unless the runtime context or repo files explicitly say .Claude/.
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 · 8 lines · 34 tokens per session scan A f27889d719b0
build is an agent published in the GitHub repository iamironz/ai-config-bundle (2 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 282 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
clippy-strict-validator
Use this agent when code changes have been made and need validation before completion or commit. Uses parallel background execution for 3-5x faster validation. Runs clippy, tests, and pattern scans simultaneously. The agent proactively ensures code quality standards are met.\n\nExamples:\n- User: "I've just added a…
error-handling-guardian
Guards structured error handling, preventing regression to anyhow and ensuring RunnerError usage.
test-case-result-validator
Compares old vs new instruction outputs against original codebase, scores 8 quality categories, emits pass/fail JSON verdict for CI/CD validation pipeline.
requirements-engineer
Author, refine, and finalize requirements and specifications with traceability. Full subagent.
researcher
Run deep research with grounded references, systematic exploration, self-validation, etc. Full subagent.
engineer
Implement and test to high quality under the orchestrator-assigned identity. Full subagent.