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/seeker71/coherence-network/spec-drivennpx skills add seeker71/Coherence-Network --skill spec-drivengit clone --depth 1 https://github.com/seeker71/Coherence-NetworkWhat 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 | $0.00042 | $0.00277 |
| Opus 5 | $0.00021 | $0.00138 |
| Sonnet 5 | $0.00008 | $0.00055 |
| Haiku 4.5 | $0.00004 | $0.00028 |
Grade A, and why
spec-driven 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 2d 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
Spec-Driven Implementation
Quick Start
- Read the spec —
specs/NNN-feature-name.mdor the spec referenced in the task - Implement only what it says — no extra features, no adjacent refactors
- Modify only listed files — see "Files to Create/Modify" in the spec
- Do not change tests — fix implementation, not tests
Constraints
- Only modify files listed in the spec's "Files to Create/Modify" section
- Do not add docs, READMEs, or refactors unless the spec requires them
- Only escalate with
needs_decisionwhen truly stuck after research; prefer fixing in-scope - Follow API Contract and Data Model from the spec exactly
Spec Format Reference
Specs follow specs/TEMPLATE.md:
- Purpose, Requirements, API Contract, Data Model
- Files to Create/Modify (the allowed set)
- Acceptance Tests, Out of Scope, Decision Gates
When Tests Fail
Fix the implementation. Do NOT modify tests to make them pass.
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.
- 2d ago First seen · 32 lines · 42 tokens per session scan A 79d30d636c6e
spec-driven is a skill published in the GitHub repository seeker71/Coherence-Network (3 stars, last pushed 6d ago), licensed Apache-2.0. It adds 42 tokens to every session and 277 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…