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 tim-mccrimmon/structured-context-spec --skill usegit clone --depth 1 https://github.com/tim-mccrimmon/structured-context-specWrote 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/tim-mccrimmon/structured-context-spec/use)<a href="https://agentmods.dev/skills/tim-mccrimmon/structured-context-spec/use"><img src="https://agentmods.dev/badge/skills/tim-mccrimmon/structured-context-spec/use/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tim-mccrimmon/structured-context-spec/use"><img src="https://agentmods.dev/badge/skills/tim-mccrimmon/structured-context-spec/use.svg" alt="Reviewed on agentmods" width="80" 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.00041 | $0.01528 |
| Opus 5.5 | $0.00016 | $0.00611 |
| Sonnet 5.5 | $0.00008 | $0.00306 |
| Haiku 4.5 | $0.00004 | $0.00153 |
Grade A, and why
use 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 28d 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 — 151 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:use. Never auto-invoke based on project state or conversation context. - Confirm before writing: After identifying the standard, present a summary of the SCDs that will be copied and the files that will be created/modified. Get explicit user confirmation before writing any files.
SCS Team Use - Add Known Standards
You are helping the user add well-known compliance or regulatory standards to their project context.
Standards Library
This plugin ships with pre-built standards SCDs. Read them from the plugin's standards/ directory rather than generating from scratch.
Available Standards
| Standard | Directory | Files |
|---|---|---|
| HIPAA | standards/hipaa/ |
hipaa-phi-handling.yaml, hipaa-security-controls.yaml, hipaa-administrative.yaml |
| SOC 2 | standards/soc2/ |
soc2-security.yaml, soc2-availability.yaml, soc2-confidentiality.yaml |
| PCI DSS | standards/pci/ |
pci-data-protection.yaml, pci-access-control.yaml, pci-monitoring.yaml |
| CHAI | standards/chai/ |
chai-transparency.yaml, chai-accountability.yaml |
| GDPR | standards/gdpr/ |
gdpr-data-rights.yaml, gdpr-processing.yaml |
Your Process
Step 1: Identify the Standard
Parse the user's request to identify which standard(s) they want:
hipaa- HIPAA compliance (healthcare, PHI)soc2- SOC2 Type II (security controls)pci- PCI-DSS (payment card data)chai- Coalition for Health AI (AI in healthcare)gdpr- General Data Protection Regulation (EU privacy)
Step 2: Read Standards from Plugin Library
Read the pre-built standards SCDs from this plugin's standards/ directory. The path is relative to this plugin's location.
To find the plugin directory: Use Glob to find **/plugins/scs-team/standards/<standard>/ and read the YAML files from there.
Step 3: Copy Standards to Project
Copy the standard SCD files to .scs/scds/ in the project:
- Create
.scs/scds/if it doesn't exist - Write each standard SCD file to the project's
.scs/scds/directory - Preserve the original content but update
provenance.created_atto current timestamp
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.
- 28d ago Changed 4023cece8d50
- 1mo ago First seen · 151 lines · 41 tokens per session scan A 80d50655dda6
use is a skill published in the GitHub repository tim-mccrimmon/structured-context-spec (19 stars, last pushed today), licensed Apache-2.0. It adds 41 tokens to every session and 1,528 once invoked, about $0.0002 per session on Opus 5.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
policy
Define and enforce decision policies, compliance rules, and exceptions over Semantica graphs. Uses ContextGraph.checkdecisionrules/enforcedecisionpolicy and context.PolicyEngine.
lex-diegosouzapw
LEX: Legal-Entity-X-ref workflow skill. Use this skill when the user needs Centralized 'Truth Engine' for cross-jurisdictional legal context (US, EU, CA) and contract scaffolding and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
lex-ignvvcio254
Centralized 'Truth Engine' for cross-jurisdictional legal context (US, EU, CA) and contract scaffolding.
code-sync
Reconcile the project's documents with what the code now shows, after a merge or at the end of a build: spec statuses (building → done only with a named gate, or → stale with the reason), assumed specs owed ratification, the project README map and its Last verified date. Surgical edits only. Use when the user says…
semantic-search
Zero-dependency TF-IDF search across MUSE memory, roles, and skills. Use when user wants to find information across their project context.
session-restore
Context restoration from .jsonl session backups. Parses history, builds chronology, saves key decisions to memory.