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/strelov1/spec-driven-tdd/spikenpx skills add strelov1/spec-driven-tdd --skill spikegit clone --depth 1 https://github.com/strelov1/spec-driven-tddWrote 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/strelov1/spec-driven-tdd/spike)<a href="https://agentmods.dev/skills/strelov1/spec-driven-tdd/spike"><img src="https://agentmods.dev/badge/skills/strelov1/spec-driven-tdd/spike.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.00484 |
| Opus 5 | $0.00018 | $0.00242 |
| Sonnet 5 | $0.00007 | $0.00097 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
spike scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
(`/tmp`, a REPL, a one-off `curl`) — **never** inside the change's worktree. What it actually says
spike
A disposable feasibility experiment. When a change carries unproven technical risk — an untested approach, an external API, an open "is this possible?" — spike it before writing any OpenSpec artifacts. The point is to answer the risky question for the price of a script, so an unviable idea is killed cheaply.
Core principle: the code is throwaway. A spike that needs cleanup was over-built. Only the verdict survives.
When to use
Risk-gated, not mandatory. Spike only when feasibility is genuinely unclear. If the approach is obviously viable, skip straight to planning. Research enough to pick an approach, then spike the riskiest unknown first — there is no point prototyping the easy parts if the hard part does not work.
Process
- Decompose — frame 2–5 concrete feasibility questions (Given/When/Then), ordered by risk. The most dangerous unknown goes first.
- Align — show the questions and the plan; let the user trim before you write code.
- Build minimal — write the smallest runnable thing in a scratch location
(
/tmp, a REPL, a one-offcurl) — never inside the change's worktree. Hardcode everything. No packaging, Docker, config, or build tooling. It is a spike. - Observe — run it and capture the real output. A spike with no observable result proved nothing.
- Verdict — close with exactly one, plus a sentence of why:
- VALIDATED — the approach works; proceed to plan the change.
- PARTIAL — only a subset works; narrow scope to that subset, then plan.
- INVALIDATED — the approach does not work; do not create the change.
After the spike
Discard the scratch code. Hand the verdict back to the caller — in the
spec-driven-tdd Plan phase it gates whether /opsx:propose runs at all.
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 · 44 lines · 37 tokens per session scan A 6e29eb112ca9
spike is a skill published in the GitHub repository strelov1/spec-driven-tdd (10 stars, last pushed 28d ago), licensed MIT. It adds 37 tokens to every session and 484 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…