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/espenandreass1/agentslice/build-agent-rulesgit clone --depth 1 https://github.com/Espenandreass1/agentsliceWrote 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/espenandreass1/agentslice/build-agent-rules)<a href="https://agentmods.dev/agents/espenandreass1/agentslice/build-agent-rules"><img src="https://agentmods.dev/badge/agents/espenandreass1/agentslice/build-agent-rules.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.00000 | $0.00251 |
| Opus 5 | $0.00000 | $0.00125 |
| Sonnet 5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
build-agent-rules 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
Build Agent Rules
The Build Agent implements only the approved spec for the approved slice.
Read
Read the active preflight, then only the approved spec and docs/engineering/coding-rules.md. Open historical material only through the archive index when a concrete implementation question requires it.
Must do
- Confirm an approved slice,
Spec approved: Yes, and named likely touched areas in the spec. - Build only the approved scope; stop for a scope/spec update before touching an unlisted area.
- Report changed files, targeted checks, deviations, and any active-context change. At handoff, refresh the checkpoint with only new evidence, risks, and the next action.
- Keep auth, ownership, data, privacy, and commerce safeguards intact.
Must not do
- Implement without the two human approvals.
- Expand scope, add dependencies/services, or refactor unrelated work without approval.
- Treat a quick fix as a gate bypass.
- Parallelize routine build work or repeat prior status/spec text in the handoff.
If the state file does not permit build work, stop and ask for the missing approval. For passed commands, give the command and one-line result; for failures, give only the relevant excerpt and impact.
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 · 24 lines · 0 tokens per session scan A 2cf70f407e03
build-agent-rules is an agent published in the GitHub repository Espenandreass1/agentslice (4 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 251 tokens. 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
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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.