Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/bnet47/codexiconnpx agentmods add skills/bnet47/codexicon/autonomous-buildWrote 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/bnet47/codexicon/autonomous-build)<a href="https://agentmods.dev/skills/bnet47/codexicon/autonomous-build"><img src="https://agentmods.dev/badge/skills/bnet47/codexicon/autonomous-build/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/skills/bnet47/codexicon/autonomous-build"><img src="https://agentmods.dev/badge/skills/bnet47/codexicon/autonomous-build.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.00020 | $0.02284 |
| Opus 5.5 | $0.00008 | $0.00914 |
| Sonnet 5.5 | $0.00004 | $0.00457 |
| Haiku 4.5 | $0.00002 | $0.00228 |
Grade A, and why
autonomous-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 1mo 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autonomous Build
Use Build for implementation requests. Work only in the current local checkout and active branch. Pure explanations and read-only reviews are exempt from this implementation workflow.
Contract
Read root SPEC.md before editing. For multi-task work, read root TASKS.md and validate both:
python scripts/codexicon.py spec-check
python scripts/codexicon.py tasks-next
If an authorized implementation has no TASKS.md, create the smallest validated
register from the root contract through $write-plan without a routine approval
stop. Use persisted states TODO, ACTIVE, BLOCKED, and DONE; queue outcomes
are READY, RESUME_ACTIVE, BLOCKED, COMPLETE, and INVALID.
Before every code generation or refactor, state the trace:
Trace: T-001 -> R-001 -> I-001
Reject or mark BLOCKED any task that cannot be traced to SPEC.md.
Decision visibility and scope gate
Record each consequential assumption or decision in the append-only journal at
agent_docs/decisions/ as a new ADR-NNN-short-title.md record. The record
must include the decision or assumption, rationale, alternatives considered,
impact, owner, date, status, and inspectable evidence. Never rewrite or delete
an accepted record; supersede it with a later record. The journal is guidance
and history, not a runtime or an authority grant.
A related correction may stay in the current task only when it is small,
reversible, directly related, and within the declared system boundary. Keep the
task trace, declared file boundary, and verification scope accurate. Otherwise
stop and explicitly escalate before editing if the change affects authority,
product behavior, schema or data shape, security posture, or an irreversible or
destructive outcome. Credentials, production actions, migrations, external
writes, publication, deployment, legal/compliance commitments, and material
architecture choices also require that escalation. $ship or the responsible
human owns those actions; a journal entry does not authorize them.
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.
- 1mo ago Changed · +12 lines 5004918a8f35
- 1mo ago Changed · +124 lines 000732df04a9
- 1mo ago Changed · +10 lines 0caebcae9b35
- 1mo ago First seen · 48 lines · 20 tokens per session scan A 6d6552a9faaf
autonomous-build is a skill published in the GitHub repository bnet47/codexicon (5 stars, last pushed 3d ago), licensed MIT. It adds 20 tokens to every session and 2,284 once invoked, about $0.0001 per session on Opus 5.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-09-09.
Other skills, from other repositories
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
team-qa
Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-tester case writing, execution, sign-off.
verification-before-completion
Use when about to claim work is complete, fixed, or passing, or before committing or creating PRs.
requirements-writer
Use when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.
scaffold-dotnet-test-project
MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up, create, reuse, add, register, include, or repair a test project. Handles "tests pass directly but CI discovers zero"…
web-app-qa
Test a web app the way a real user would: click through the main flows, try odd inputs, watch for errors, and keep screenshots as proof. You get a bug report ranked by how serious each problem is.