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/initnpx skills add tim-mccrimmon/structured-context-spec --skill initgit 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.00033 | $0.02174 |
| Opus 5 | $0.00016 | $0.01087 |
| Sonnet 5 | $0.00007 | $0.00435 |
| Haiku 4.5 | $0.00003 | $0.00217 |
Grade A, and why
init 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 3d 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 — 252 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:init. Never auto-invoke based on project state or conversation context. - Confirm before writing: After scanning the project, present a summary of the
.scs/scaffold you plan to create and get explicit user confirmation before writing any files.
SCS Team Init - Initialize Structured Context
You are scaffolding a new .scs/ directory for this project. This is the entry point for teams adopting structured context.
Your Process
Step 1: Detect Project Info
Scan the project to understand what exists:
Language/Framework Detection (check in order):
package.json→ Node.js (check for Next.js, React, Express, etc.)requirements.txtorpyproject.tomlorsetup.py→ Python (check for FastAPI, Django, Flask)go.mod→ GoCargo.toml→ Rustpom.xmlorbuild.gradle→ Java/KotlinGemfile→ Ruby.csprojor.sln→ .NET
Existing Documentation (scan for):
docs/,doc/,documentation/directories- Root-level:
PRD.md,ARCHITECTURE.md,SECURITY.md,README.md - Any
*.mdfiles that look like project documentation CLAUDE.md,.claude/rules/(existing Claude context)
Compliance Signals (look for keywords in docs and code):
- HIPAA: "PHI", "protected health information", "HIPAA", "healthcare"
- SOC2: "SOC2", "SOC 2", "trust service criteria"
- PCI: "PCI", "cardholder", "payment card"
- GDPR: "GDPR", "personal data", "data subject"
- CHAI: "clinical AI", "health AI", "CHAI"
Step 2: Determine Project Name
Use the argument if provided. Otherwise:
- Check
package.jsonname field - Check
pyproject.tomlproject name - Check
go.modmodule name - Fall back to directory name
Step 3: Create .scs/ Scaffold
Create the following structure:
.scs/
├── project.yaml # Project bundle manifest
├── concerns/
│ ├── architecture.yaml
│ ├── security.yaml
│ ├── performance.yaml
│ ├── usability.yaml
│ ├── compliance.yaml
│ ├── data.yaml
│ ├── testing.yaml
│ ├── deployment.yaml
│ ├── safety.yaml
│ ├── ethics.yaml
│ └── business.yaml
└── scds/ # Empty - populated by add/draft/use
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.
- 3d ago First seen · 252 lines · 33 tokens per session scan A 03de31fe05c2
init 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 33 tokens to every session and 2,174 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-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.