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/statusnpx skills add tim-mccrimmon/structured-context-spec --skill statusgit 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/status)<a href="https://agentmods.dev/skills/tim-mccrimmon/structured-context-spec/status"><img src="https://agentmods.dev/badge/skills/tim-mccrimmon/structured-context-spec/status.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 | $0.00031 | $0.01760 |
| Opus 5 | $0.00015 | $0.00880 |
| Sonnet 5 | $0.00006 | $0.00352 |
| Haiku 4.5 | $0.00003 | $0.00176 |
Grade A, and why
status 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 4d 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 — 181 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:status. Never auto-invoke based on project state or conversation context.
SCS Team Status - Context Overview
You are showing the user what structured context exists for their project and highlighting gaps.
Your Process
Step 1: Scan for Existing Context
Look for SCS artifacts:
.scs/directory (bundles, concerns, SCDs).claude/rules/directory (compiled output)CLAUDE.md(might have scs-team managed section)
Step 2: Inventory What Exists
For each bundle found:
- Bundle ID and type
- Version (DRAFT or semantic version)
- SCDs it contains
- What it imports
For each SCD found:
- SCD ID and tier
- What concern it addresses
- Version status
Step 3: Assess Coverage Against All 11 Concerns
Map what exists to the full concern model:
| # | Concern | Expected SCDs | Status |
|---|---|---|---|
| 1 | Architecture | system-context, tech-stack, integration-map, component-model | Covered / Partial / Missing |
| 2 | Security | authn-authz, data-protection, data-handling, threat-model | Covered / Partial / Missing |
| 3 | Performance & Reliability | response-time, availability, fault-tolerance, scalability | Covered / Partial / Missing |
| 4 | Usability & Accessibility | ux-principles, accessibility-compliance, error-handling-ux | Covered / Partial / Missing |
| 5 | Compliance & Governance | hipaa-compliance, soc2-controls, audit-requirements, policy-enforcement | Covered / Partial / Missing |
| 6 | Data & Provenance | data-model, provenance-tracking, retention-policy | Covered / Partial / Missing |
| 7 | Testing & Validation | test-coverage, validation-plan, qa-procedures | Covered / Partial / Missing |
| 8 | Deployment & Operations | infrastructure-definition, observability, incident-response | Covered / Partial / Missing |
| 9 | Safety & Risk | risk-assessment, safety-checklist | Covered / Partial / Missing |
| 10 | Ethics & AI Accountability | ai-usage-policy, audit-trail, model-bias | Covered / Partial / Missing |
| 11 | Business Context | problem-definition, stakeholders, business-objectives, opportunity-analysis, constraints-and-assumptions, success-criteria | Covered / Partial / Missing |
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.
- 4d ago First seen · 181 lines · 31 tokens per session scan A 999c28d24ada
status 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 31 tokens to every session and 1,760 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
reflect
Session reflection — analyzes what happened, proposes backlog items, captures insights.
system-audit
Periodic evidence-based self-audit of the whole agent system — the orchestrator, its docs/SSOTs, rules, memory, subagents, tools, infra and the work it claims to have delivered — followed by immediate cheap-safe fixes and a ranked backlog. Use when the user says 'аудит системы', 'проверь себя', 'самопроверка', 'system…
gh-cli-projects-tasks-conventions
How The Lossless Group uses the gh CLI for GitHub issues and Projects v2 tasks across the pseudomonorepo tree. Use whenever creating, editing, or listing GitHub Project tasks via gh project item-create, gh project item-add, or gh project item-edit; whenever creating repo issues via gh issue create; whenever the user…
qa-sweep
Run a multi-lens agent QA sweep of the RUNNING product: spawn qa agents (one per lens — user-flow · edge-state · honesty · contract · ux-critique), collect their structured findings, integrator-verify the load-bearing ones, and land verified findings as backlog tickets + a run record in the project's qa/ folder. Use…
gh
Install and configure the GitHub CLI (gh) for AI agent environments where gh may not be pre-installed and git remotes use local proxies instead of github.com. Provides auto-install script with SHA256 verification and GITHUBTOKEN auth with anonymous fallback. Use when gh command not found, shutil.which("gh") returns…
02-user-stories
Produces or refines ordered User Stories from an Epic, Product Brief, PRD, or bounded request. Use when the user wants to slice, write, assess, order, or persist Stories. Not for Epics or implementation.