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/stoa-platform/stoa/spec-drivennpx skills add stoa-platform/stoa --skill spec-drivengit clone --depth 1 https://github.com/stoa-platform/stoaWhat 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.00025 | $0.00571 |
| Opus 5 | $0.00013 | $0.00285 |
| Sonnet 5 | $0.00005 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven Development
CAB-2005: Formalize the spec-first pattern. Council validates the spec BEFORE code. Acceptance criteria become test cases. Tests are written BEFORE implementation.
Usage
/spec-driven CAB-XXXX
/spec-driven "feature description"
Step 1: Create Spec
- If a CAB-XXXX ID is given, fetch the ticket from Linear:
linear.get_issue("CAB-XXXX") - Copy template from
.claude/templates/SPEC.md - Fill in: Problem, Goal, API Contract, Acceptance Criteria, Edge Cases
- Write to branch root as
SPEC.md
Step 2: Council on Spec (Stage 1 variant)
Run the 4-persona Council but evaluate the spec quality, not the feature itself:
- Chucky: Are edge cases covered? Missing failure modes?
- OSS Killer: Is the goal measurable? Will this deliver user value?
- Archi: Is the API contract consistent with existing patterns? Breaking changes?
- Better Call Saul: Security considerations complete? PII/GDPR noted?
Threshold: >= 7.0 to proceed. Below 7.0: revise spec first.
Step 3: Generate Failing Tests
From each acceptance criterion, generate a test:
- Python (api):
test_spec_ac1_<description>()intests/test_spec_<ticket>.py - TypeScript (ui/portal):
describe('spec/CAB-XXXX', () => { it('AC1: ...') })insrc/__tests__/spec/ - Rust (gateway):
fn spec_ac1_description()in inline#[cfg(test)] mod tests
All tests MUST fail (red) at this stage. If any passes, the criterion is already met or the test is wrong.
Step 4: Implement
Write code to make all tests pass. Standard Pattern 3 workflow.
Step 5: Verify
- All spec tests green
- No other tests broken
SPEC.mdstays in the branch (committed with the PR) as documentation
Rules
- Spec lives in branch root, committed in the same PR as the implementation
- Council scores the spec, not the implementation plan
- Every acceptance criterion = exactly one test
- Edge cases table = additional tests (tagged
@edge-case) - If spec changes during implementation, re-run Council
.spec.md= technical only. Business data → stoa-strategy (private repo)
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 · 65 lines · 25 tokens per session scan A 9372f6d19111
spec-driven is a skill published in the GitHub repository stoa-platform/stoa (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 571 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
lyrik
Security assessment of a codebase — minimal mode for runner validation.
librarian
Read-only retrieval over the daily-digest kept set. Slash-invoke with /librarian ; returns items verbatim with citations.
notes
Create and manage text notes in the workspace.
tdx-assets
Look up staff devices, assets, and locations in TeamDynamix (TDX). Given a list of names, emails, or partial identifiers, resolve each person and return the assets assigned to them with location, model, ownership type, and status. Read-only.
aggregator
Daily fetch from a fixed public allowlist; score against the user's interests file; cluster into themes; push the digest to the configured channel.
csv-tools
Parse and analyze CSV data.