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/lucasviola/specwiki/ship-vertical-slicenpx skills add lucasviola/specwiki --skill ship-vertical-slicegit clone --depth 1 https://github.com/lucasviola/specwikiWrote 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/lucasviola/specwiki/ship-vertical-slice)<a href="https://agentmods.dev/skills/lucasviola/specwiki/ship-vertical-slice"><img src="https://agentmods.dev/badge/skills/lucasviola/specwiki/ship-vertical-slice.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.00037 | $0.00400 |
| Opus 5 | $0.00018 | $0.00200 |
| Sonnet 5 | $0.00007 | $0.00080 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
ship-vertical-slice 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
Ship vertical slice
Ship one thin end-to-end path before polishing edge cases or refactoring.
Slice template
Input (CLI args)
→ validate / parse
→ carrier adapter (fixture or client)
→ domain types (TrackingEvent[])
→ formatTimeline() + next-action copy
→ stdout + exit code
Workflow
- Write the test first — one happy-path integration test from argv to expected stdout.
- Implement the narrowest path — skip flags you do not need yet.
- Add one failure test — bad id, unknown carrier, or adapter throw.
- Document user-facing changes — README flag table + example command.
- Run the session checklist from
CLAUDE.md:npm testbefore and after- Re-run only the tests you touched if iterating
Scope guardrails
- Do not add a database, web UI, or label printing in the same slice.
- Do not refactor unrelated carriers — leave drive-by cleanups for a separate PR.
- Keep diffs commit-sized; if the slice spans more than ~3 files, split it.
Exit codes (do not change casually)
| Code | Meaning |
|---|---|
0 |
Success |
1 |
Usage / validation (bad args, unknown flag) |
2 |
Carrier or runtime failure |
Done when
- Happy + one failure path covered
- README updated for anything users type differently
- Verbose output still PII-safe (run
/review-pii-redactionif you added logging)
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 · 52 lines · 37 tokens per session scan A f1c90373c070
ship-vertical-slice is a skill published in the GitHub repository lucasviola/specwiki (11 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 400 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-30.
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…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…