Q00/ouroboros is an Agent OS for running coding agents through interviews, staged evaluation, and repeated improvement cycles. It helps developers turn vague requests into tested code across multiple agent runtimes. Its catalogue add-ons provide workflows, agents, hooks, instructions, and integrations for operating those processes.
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 Q00/ouroboros --skill resume-sessiongit 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/resume-session)<a href="https://agentmods.dev/skills/q00/ouroboros/resume-session"><img src="https://agentmods.dev/badge/skills/q00/ouroboros/resume-session.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00022 | $0.01038 |
| Opus 5 | $0.00011 | $0.00519 |
| Sonnet 5 | $0.00004 | $0.00208 |
| Haiku 4.5 | $0.00002 | $0.00104 |
Grade A, and why
resume-session 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 5d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ouroboros:resume-session
Recover in-flight Ouroboros sessions after an unexpected MCP server disconnect.
Claude Code reserves /resume for its built-in session picker. This skill
intentionally uses resume-session so it does not shadow that native command.
Usage
ooo resume-session
ooo resume-session --all
/ouroboros:resume-session
Trigger keywords: "in-flight Ouroboros sessions", "re-attach", "mcp disconnected", "lost Ouroboros execution"
How It Works
ooo resume-session reads the EventStore directly (no MCP server required) and lists
every session that is still in a running or paused state. The command is
strictly read-only — it never creates the data directory, never writes
schema, and never appends events. Its job is to surface the identifiers you
need to re-attach.
ooo resume-sessionshows the 20 most recent active sessions.ooo resume-session --allshows every active session.
Instructions
When the user invokes this skill:
-
Run the CLI command:
ouroboros resumeThis reads the configured runtime EventStore directly — the MCP server does not need to be running.
-
If sessions are listed, enter the number of the session you want to work with. The command prints both the
session_idand theexec_id, along with the available re-attach paths. -
Pick the right re-attach path:
-
Inspect persisted events (read-only):
ouroboros status execution <exec_id> --eventsReads the configured EventStore without starting an MCP server.
-
Inspect interactively (read-only monitor):
ouroboros tui monitorLaunches the TUI and lets you pick the session to inspect.
-
Resume execution (requires the original seed file):
ouroboros run workflow --orchestrator --resume <session_id> <seed.yaml>
-
Exit codes
| Code | Meaning |
|---|---|
0 |
Success — sessions listed, or no sessions found |
1 |
Invalid user selection (non-numeric or out-of-range) |
2 |
EventStore exists but could not be opened or read |
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.
- 5d ago Changed · +14 lines 2b19252b0931
- 8d ago First seen · 121 lines · 22 tokens per session scan A 3f9bb26ba6db
resume-session is a skill published in the GitHub repository Q00/ouroboros (5,789 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 1,038 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
adaptive-quality
Per-task execution profile selection based on complexity in Balanced quality mode.
auto-qa
QAMESH project QA mesh — plan, run, report, and publish deterministic QA evidence.
experiment
Experiment loop for iterative metric-driven code optimization using XLOOP.
ci-cd
A guide for designing automated build and delivery workflows with GitHub Actions. These workflows can run checks such as tests, code-quality scans, coverage checks, and builds when code is pushed or a pull request is opened.
metrics
North Star Metric, input metrics, and success dashboard design.
auto-fix
A bug-fixing workflow that first reproduces a problem with a test, then applies the smallest code change needed. It also checks the related code path and runs tests afterward.