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.
git 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/plugins/tim-mccrimmon/structured-context-spec/scs-team)<a href="https://agentmods.dev/plugins/tim-mccrimmon/structured-context-spec/scs-team"><img src="https://agentmods.dev/badge/plugins/tim-mccrimmon/structured-context-spec/scs-team/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/plugins/tim-mccrimmon/structured-context-spec/scs-team"><img src="https://agentmods.dev/badge/plugins/tim-mccrimmon/structured-context-spec/scs-team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
scs-team 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 1mo 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.
What it actually says
{
"name": "scs-team",
"description": "Structured Context for Teams - Initialize, build, validate, and version structured context from your PRDs, architecture docs, and compliance requirements. Compiles to Claude Code rules automatically.",
"version": "2.0.0",
"author": {
"name": "Tim McCrimmon",
"email": "[email protected]"
},
"homepage": "https://structuredcontext.dev",
"repository": "https://github.com/tim-mccrimmon/structured-context-spec/tree/main/plugins/scs-team",
"license": "Apache-2.0",
"keywords": [
"structured-context",
"scs",
"governance",
"compliance",
"architecture",
"teams",
"enterprise",
"hipaa",
"soc2",
"context"
]
}
What it installs
The manifest is a name and a version. 7 skills travel with it, and installing the plugin installs all of them — 208 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 25 lines scan A 998d58322895
scs-team is a plugin published in the GitHub repository tim-mccrimmon/structured-context-spec (18 stars, last pushed 18d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
memory-kit
Persistent memory for your agent as plain files in your folder: a hot cache injected every session and held under three size caps, per-session handoffs, and promotion into knowledge articles and rules only on your yes. Carries the builder's layers too — executor/recon/idea-validator agents, session review, second…
memory-toolkit
Session memory lifecycle for developers — structured markdown memory, workstreams, handoff, auto-save hooks. No vector DB, no external dependencies.
ai-context-kit marketplace
Context-aware AI collaboration skills for creating and validating user context, project AGENTS.md files, and skill artifacts across LLM providers.
ai-context-kit
Context-aware AI collaboration skills and implementation loop prompts for creating and validating user context, project AGENTS.md files, and skill artifacts across LLM providers.
claude-ryzome
Ryzome — AI context library. Create, retrieve, and manage canvases and documents for externalizing agent working memory.
aictx
Use AICTX repo-local operational continuity in Claude Code.