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 skills add komluk/scaffolding --skill spec-researchgit clone --depth 1 https://github.com/komluk/scaffoldingWrote 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/komluk/scaffolding/spec-research)<a href="https://agentmods.dev/skills/komluk/scaffolding/spec-research"><img src="https://agentmods.dev/badge/skills/komluk/scaffolding/spec-research.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.00051 | $0.00733 |
| Opus 5 | $0.00026 | $0.00367 |
| Sonnet 5 | $0.00010 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
spec-research 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 7d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSpec Proposal Writing
Guide for creating proposal.md -- the WHY document that anchors the entire workflow.
Output Path
Write to: {specs_path}/proposal.md
Path Enforcement: The specs_path MUST be .scaffolding/conversations/{UUID}/specs/ where {UUID} is a valid UUID (format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). NEVER use descriptive folder names.
Required Sections
| Section | Purpose | Content |
|---|---|---|
| Why | Motivation | 1-2 sentences. What problem? Why now? |
| What Changes | Scope | Bullet list. New capabilities, modifications, removals. Mark BREAKING |
| Capabilities | Contract | New + modified capabilities (kebab-case names) |
| Impact | Blast radius | Affected code, APIs, dependencies, systems |
| Agent Assignment | Routing | Table of agents, roles, artifacts |
| Rollback Plan | Safety | Revert points, manual steps, affected systems |
Capabilities Section (Critical)
This section creates the contract between proposal and design phases.
New Capabilities
- Use kebab-case:
user-auth,data-export,api-rate-limiting - Each becomes a requirement group in design.md
- Brief description of what the capability covers
Modified Capabilities
- Only list if spec-level REQUIREMENTS change (not just implementation)
- Check
.scaffolding/openspec/specs/for existing names - Leave empty if no requirement changes
Quality Checklist
- Goals are concrete and measurable (not vague)
- Edge cases identified in Impact section
- All affected agents listed in Agent Assignment
- Rollback plan has specific revert steps
- Capabilities use kebab-case naming
- No implementation details (those go in design.md)
- Stakeholder impact addressed
Template Structure
## Why
[1-2 sentences: problem + urgency]
## What Changes
- [Specific change 1]
- [Specific change 2]
- **BREAKING**: [Breaking change, if any]
## Capabilities
### New Capabilities
- `capability-name`: Brief description
### Modified Capabilities
- `existing-name`: What requirement is changing
## Impact
[Affected code, APIs, dependencies, systems]
## Agent Assignment
| Agent | Role | Artifacts |
|-------|------|-----------|
| architect | Analyst + Coordinator | proposal.md, design.md, tasks.md |
| researcher | External Research (if needed) | ResearchPack |
| developer | Developer | Source code |
| reviewer | Reviewer | Review report |
## Rollback Plan
- [ ] Identify revert points
- [ ] Document manual rollback steps
- [ ] List affected systems
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.
- 7d ago First seen · 99 lines · 51 tokens per session scan A 83497bf7ad0b
spec-research is a skill published in the GitHub repository komluk/scaffolding (15 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 733 once invoked, about $0.0003 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
turnstile-loop-start
Starts a goal-directed loop run -- asks for mode, initialises state.json, then dispatches loop-runner repeatedly until the success condition is met, max-iterations is reached, or an unrecoverable error occurs.
turnstile-loop-status
Reads turnstile/loops/ /state.json and renders the current phase, status, and full iteration history in the terminal.
turnstile-brain-init
Opt-in bulk bootstrap of turnstile/code/ -- one linked note per source file. The default pipeline is lazy (code notes only for ticket-touched files, written when the ticket passes review); this is the eager exception. Dispatched by /turnstile:brain-init only.
turnstile-brain
Vault layout, the shared note format, and the check-the-brain-first mandate. Auto-loads whenever any turnstile skill starts new work or /turnstile:review is about to commit.
turnstile-conversate
Entry point for natural-language turnstile requests -- classifies the message against board state, then answers directly or invokes the one matching skill (brainstorm, quick, refine, spec, sprint-plan, work, review, breakdown, drop, systematic-debugger, code-reviewer).
turnstile-work
Implements one sprint ticket via TDD and the turnstile-coder agent, checking the brain first. Dispatched by /turnstile:work or conversate routing only.