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 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/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/espenandreass1/agentslice/write-build-spec"><img src="https://agentmods.dev/badge/skills/espenandreass1/agentslice/write-build-spec.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.00024 | $0.00222 |
| Opus 5.5 | $0.00010 | $0.00089 |
| Sonnet 5.5 | $0.00005 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
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 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.
What it actually says
Write Build Spec
Read
Verify the workspace and minimal preflight. Read the formal PR, policy, coding rules, and planning context. Open one historical record only for a concrete unresolved constraint.
Guardrails
- Use this for
controlled-change, audit-sensitive, or unusually risky work—not ordinary docs, fast bugs, or bounded features. - The PR remains the live status source.
- Require human controlled plan/spec approval before sensitive implementation proceeds.
- Keep the spec around 120 lines or fewer; explain a longer record by risk.
Steps
- Link the PR and state the user problem, touched/must-not-touch areas, policy trigger, acceptance, QA, and rollback.
- Set human approval evidence in the PR and planning state only when it is active planning.
- Stop for explicit controlled plan/spec approval.
Output
Link the compact plan and request approval. Do not duplicate PR status or create an unnecessary checkpoint.
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 · -3 lines · -10 tokens per session 01fec1a9fa6c
- 1mo 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 1mo ago), licensed MIT. It adds 24 tokens to every session and 222 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-08-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…