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 skills/espenandreass1/agentslice/write-build-specnpx skills add Espenandreass1/agentslice --skill write-build-specgit 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/skills/espenandreass1/agentslice/write-build-spec)<a href="https://agentmods.dev/skills/espenandreass1/agentslice/write-build-spec"><img src="https://agentmods.dev/badge/skills/espenandreass1/agentslice/write-build-spec.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.1 | $0.00034 | $0.00327 |
| Opus 5 | $0.00017 | $0.00163 |
| Sonnet 5 | $0.00007 | $0.00065 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
write-build-spec 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 6d 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
Write Build Spec
Read
Read the active preflight, then planning context (vision.md, tech-stack.md, live next-slices.md) and the spec template. Read qa-plan.md only to select checks for the proposed spec. Use archive records only through the index for a concrete unresolved constraint.
Guardrails
- Confirm an approved slice and phase
SLICE_APPROVED; otherwise stop. - Do not implement. Set
Spec approved: Noand phaseSPEC_DRAFTEDafter drafting. - Keep a small spec to about 120 lines or fewer. If risk requires more, explain why and link to focused supporting material.
- Name likely touched areas, must-not-change areas, observable acceptance criteria, risks, and QA checks.
- Do not parallelize this sequential planning step.
Steps
- Convert the approved slice into the smallest concrete spec.
- Link to current slice, active context, and only directly relevant decisions instead of copying them.
- Choose focused QA checks and identify an exact trigger for a full suite, or record why focused scope is sufficient.
- Update
current-slice.md,active-context.md,workflow-state.md, and checkpoint. - Stop for explicit human spec approval.
Output
Present the compact spec and ask to approve, reject, or adjust it before build starts. Link to active context rather than repeat it.
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.
- 6d ago First seen · 31 lines · 34 tokens per session scan A 075386d3243e
write-build-spec is a skill published in the GitHub repository Espenandreass1/agentslice (4 stars, last pushed 11d ago), licensed MIT. It adds 34 tokens to every session and 327 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…