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/pawel-kica/claude-code-100/spec-implementnpx skills add Pawel-Kica/claude-code-100 --skill spec-implementgit clone --depth 1 https://github.com/Pawel-Kica/claude-code-100Wrote 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/pawel-kica/claude-code-100/spec-implement)<a href="https://agentmods.dev/skills/pawel-kica/claude-code-100/spec-implement"><img src="https://agentmods.dev/badge/skills/pawel-kica/claude-code-100/spec-implement.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.00023 | $0.00255 |
| Opus 5 | $0.00012 | $0.00128 |
| Sonnet 5 | $0.00005 | $0.00051 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
spec-implement 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
Implement the work described in the spec.
Start
- List
~/.claude/specs/. Match arg against folder names +spec.md. One → use. Many → list, ask. None → stop. - Copy ONLY
spec.md-> repodocs/specs/<name>.md.
Build
- Stay on
main. Dirty tree OK - other agents' WIP lives here too, no new branch. - Follow repo
CLAUDE.mdconventions rigorously before first edit. - Use subagents where needed for context efficiency.
- Always proceed. Stop only on a huge blocker (rare).
Finish
- Verify via
/e2eif possible. Skip only if the change has nothing to drive. - Run
/super-code-reviewand fix everything worth doing. - Recap 2-4 lines: what changed.
Hard limit
Local only on main. No commit, push, PR. Changes sit uncommitted. The user reviews in their editor, then ships.
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 · 26 lines · 23 tokens per session scan A 404e3fe1580d
spec-implement is a skill published in the GitHub repository Pawel-Kica/claude-code-100 (2 stars, last pushed 13d ago), licensed MIT. It adds 23 tokens to every session and 255 once invoked, about $0.0001 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…
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…