Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/bradheitmann/odin-sentinelnpx agentmods add skills/bradheitmann/odin-sentinel/odin-scpWrote 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/bradheitmann/odin-sentinel/odin-scp)<a href="https://agentmods.dev/skills/bradheitmann/odin-sentinel/odin-scp"><img src="https://agentmods.dev/badge/skills/bradheitmann/odin-sentinel/odin-scp/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/bradheitmann/odin-sentinel/odin-scp"><img src="https://agentmods.dev/badge/skills/bradheitmann/odin-sentinel/odin-scp.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.00149 | $0.31104 |
| Opus 5.5 | $0.00060 | $0.12442 |
| Sonnet 5.5 | $0.00030 | $0.06221 |
| Haiku 4.5 | $0.00015 | $0.03110 |
Grade A, and why
odin-scp 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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- odin-scp — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 1,875 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sentinel Coordination Protocol
SCP_PUBLIC_VERSION: 0.8.0 MIN_COMPATIBLE_CHILD_MCP: 0.4.5
Public install readiness: configure the ODIN MCP server, install native skill context where supported or use full prompt fallback, keep governed team roles in CMUX, verify auth/account readiness without printing secrets, smoke-test local inference if used, and validate role compatibility before launch. Installed runtime skill copies are synchronized snapshots of the canonical skill, and a copy that differs from it is stale and must be re-synced; public release checks compare repo-internal public artifacts.
Use this skill for SCP policy introduction, repo landing, adoption-gate proof, controlled dissemination, active multi-agent control loops, and automated team lifecycle management. SCP is a governance layer for multi-team agent operation; it complements other coordination layers and AGENTS.md files where present. It sits above them after activation.
Source Of Truth
Master editable source:
- the repository-distributed SCP protocol bundle, or an operator-declared canonical SCP skill source outside this public package.
The active canonical SCP skill directory is the directory that contains this SKILL.md plus its references/, agents/, and scripts/ support files.
All installed copies are synchronized runtime snapshots, not independent policy forks. Any agent modifying SCP policy must edit the declared source first, then propagate the full skill/protocol bundle to the installed harness targets and verify matching hashes.
Use the operator-declared sync procedure after edits. Do not hand-edit generated runtime copies except as a temporary emergency patch that is immediately backported to the declared source and resynced.
Portable curated skill/session records may live under the declared source, for example decisions/YYYY-MM-DD-<slug>.md and optionally CHANGELOG.md. Raw audit evidence belongs under .odin/audit/<session-id>/ or the declared evidence_path. Do not create empty folders just to satisfy policy; create decisions/ only when writing the first curated decision record.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago Changed cc2b35fde45d
- 1mo ago Changed b73444ab76d6
- 1mo ago Changed d4a10a46bbc4
- 1mo ago Changed · +27 lines · -3 tokens per session af7633b57319
- 2mo ago First seen · 1,848 lines · 152 tokens per session scan A ad21f2b37463
odin-scp is a skill published in the GitHub repository bradheitmann/odin-sentinel (2 stars, last pushed 10d ago), licensed MIT. It adds 149 tokens to every session and 31,104 once invoked, about $0.0006 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-31.
Other skills, from other repositories
sprint-status
Track parallel work sessions and prevent confusion across multiple Claude Code instances. Every major step ends with a status line. Every question re-states project, branch, and task.
bug-capture
Capture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the codebase in parallel for context but never leaks file paths or line numbers into the issue. Use when the user reports a bug conversationally, runs a QA pass, or says "file an issue", "log this as a bug"…
session-handoff
Generate a structured handoff document capturing current progress, open tasks, key decisions, and context needed to resume work. Use when ending a session, saying "continue later", "save progress", "session summary", or "pick up where I left off".
god-plan
Write or refresh .godpowers/PLAN.md with the goal, requirements that each have a "Done when" check, non-goals, design, and thin vertical slices. Use for /god-plan, "plan this", or before building a feature or product.
god
Godpowers front door. Reads .godpowers/STATE.md and either names the next step or drives a goal through only the stages it needs. Use for /god, "what next", or "take this to production".
god-init
Set up Godpowers in the current repo (.godpowers/ state, decision log, evidence ledger) or migrate a Godpowers 6 project to the 7 layout. Use for /god-init, "set up godpowers", or when /god finds no project.