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/tim-mccrimmon/structured-context-spec/draftnpx skills add tim-mccrimmon/structured-context-spec --skill draftgit clone --depth 1 https://github.com/tim-mccrimmon/structured-context-specWhat 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.02313 |
| Opus 5 | $0.00013 | $0.01156 |
| Sonnet 5 | $0.00005 | $0.00463 |
| Haiku 4.5 | $0.00003 | $0.00231 |
Grade A, and why
draft 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Invocation Rules
- User-initiated only: Do NOT invoke this skill unless the user explicitly runs
/scs-team:draft. Never auto-invoke based on project state or conversation context. - Confirm before writing: After the conversation, present a summary of the SCDs you plan to generate and the files you'll create/modify. Get explicit user confirmation before writing any files.
SCS Team Draft - Conversational Context Creation
You are helping the user create structured context for a specific concern area through conversation. Use this when they don't have existing documentation.
The 11 Concerns
| # | Concern | Slug | What It Covers |
|---|---|---|---|
| 1 | Architecture | architecture |
System structure, components, boundaries, tech stack |
| 2 | Security | security |
Auth, data protection, threats, access control |
| 3 | Performance & Reliability | performance |
Response times, availability, fault tolerance, scaling |
| 4 | Usability & Accessibility | usability |
UX principles, accessibility, error handling patterns |
| 5 | Compliance & Governance | compliance |
Regulatory requirements, audit, governance |
| 6 | Data & Provenance | data |
Data models, data flow, retention, provenance |
| 7 | Testing & Validation | testing |
Test strategy, coverage requirements, validation approach |
| 8 | Deployment & Operations | deployment |
Infrastructure, CI/CD, environments, monitoring |
| 9 | Safety & Risk | safety |
Risk assessments, safety checklists, mitigation strategies |
| 10 | Ethics & AI Accountability | ethics |
AI usage policies, bias detection, audit trails |
| 11 | Business Context | business |
Problem definition, stakeholders, objectives, success criteria |
Your Process
Step 1: Understand Current State
Before asking questions:
- Check what context already exists (
.scs/directory) - Scan the codebase to understand what's already built
- Note any existing patterns or choices
Step 2: Ask Targeted Questions
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 · 224 lines · 25 tokens per session scan A 3cd76dcc9049
draft is a skill published in the GitHub repository tim-mccrimmon/structured-context-spec (19 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 2,313 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-30.
Other skills, from other repositories
good-skill
Use only for fixture validation of narrow skill routing. Avoid for normal repo work.
broad-skill
Always use this skill for every task and all tasks.
caveman-fixture
Always use caveman terse speech for every task.
acontext-installer
Install Acontext, Login & Init Acontext Project, Add Skill Memory to Agent.
missing-description
No description.
semantic-search
Zero-dependency TF-IDF search across MUSE memory, roles, and skills. Use when user wants to find information across their project context.