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/q00/ouroboros/statusnpx skills add Q00/ouroboros --skill statusgit clone --depth 1 https://github.com/Q00/ouroborosWrote 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/q00/ouroboros/status)<a href="https://agentmods.dev/skills/q00/ouroboros/status"><img src="https://agentmods.dev/badge/skills/q00/ouroboros/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.00012 | $0.01119 |
| Opus 5 | $0.00006 | $0.00560 |
| Sonnet 5 | $0.00002 | $0.00224 |
| Haiku 4.5 | $0.00001 | $0.00112 |
Grade A, and why
ouroboros-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 2d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ouroboros:ouroboros-status
Check session status and measure goal drift.
Usage
/ouroboros:ouroboros-status [session_id]
Trigger keywords: "am I drifting?", "session status", "drift check"
How It Works
- Session Status: Queries the current state of an execution session
- Drift Measurement: Measures how far the execution has deviated from the original seed goal
Instructions
When the user invokes this skill:
Load MCP Tools (Required first)
The Ouroboros MCP tools are often registered as deferred tools that must be explicitly loaded before use. You MUST perform this step before proceeding.
- Use the active runtime's tool-discovery capability to find and load the status MCP tools:
tool discovery query: "+ouroboros session status" - The tools will typically be named with prefix
mcp__plugin_ouroboros_ouroboros__(e.g.,ouroboros_session_status,ouroboros_measure_drift). After runtime tool discovery returns, the tools become callable. - If the tools are callable — already exposed, or loaded by discovery — proceed with the steps below. An empty discovery result for already-exposed tools is expected, not a failure. Skip to the Fallback section only if they are genuinely absent (no Ouroboros MCP server).
IMPORTANT: Do NOT skip this step. Do NOT assume MCP tools are unavailable just because they don't appear in your immediate tool list. They are almost always available as deferred tools that need to be loaded first.
Status Steps
-
Determine the session to check:
- If
session_idprovided: Use it directly - If no session_id: Check conversation for recent session IDs
- If none found: Ask user for the session ID
- If
-
Call
ouroboros_session_statusMCP tool:Tool: ouroboros_session_status Arguments: session_id: <session ID> -
If the user asks about drift (or says "am I drifting?"), also call
ouroboros_measure_drift:Tool: ouroboros_measure_drift Arguments: session_id: <session ID> current_output: <current execution output or file contents> seed_content: <original seed YAML> constraint_violations: [] (any known violations) current_concepts: [] (concepts in current output)
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.
- 2d ago Changed · +10 lines fc6631532997
- 4d ago First seen · 123 lines · 12 tokens per session scan A ef19e086db8a
ouroboros-status is a skill published in the GitHub repository Q00/ouroboros (5,765 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 1,119 once invoked, about $0.0001 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
release-rome-image
Release a new Rome runtime image by pushing a vX.Y.Z tag — pick the version, verify main is releasable, push the tag, and confirm the image published to Docker Hub. Covers the v runtime-image tag only, not the desktop app (desktop-v) and not npm packages (ui-v, app-runtime-v).
beevibe-team-mesh-negotiation
Multi-round negotiation protocol — covers both initiator and peer roles. Use when about to call negotiate(), when receiving a intent block as a peer, or when receiving an 'escalated' sentinel from a blocked respondnegotiate. Covers proposal crafting, counter-strategy, deadlock detection, when to accept early…
prep
Session wrap-up. Update memories, check plans, review git state, check inbox, flag loose ends. Use before closing a session or compacting context.
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries.
system_status
Check system health -- disk usage, memory, running processes, uptime.
branch_health
Quick health check -- test counts and file stats for AIPass branches.