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 publishgit 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/publish)<a href="https://agentmods.dev/skills/q00/ouroboros/publish"><img src="https://agentmods.dev/badge/skills/q00/ouroboros/publish/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/q00/ouroboros/publish"><img src="https://agentmods.dev/badge/skills/q00/ouroboros/publish.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.01541 |
| Opus 5.5 | $0.00006 | $0.00616 |
| Sonnet 5.5 | $0.00003 | $0.00308 |
| Haiku 4.5 | $0.00001 | $0.00154 |
Grade A, and why
publish 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 6d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ouroboros:publish
Convert a Seed into a GitHub Epic issue plus Task issues. Works entirely through the gh CLI (no MCP), creates new issues only, and never modifies existing ones.
ooo publish [seed_path]
/ouroboros:publish [seed_path]
Instructions
Run commands with the active runtime's run_shell capability and ask every question with the active runtime's ask_user capability.
Step 1: Prerequisites
Run command -v gh. If missing, tell the user to install it from https://cli.github.com/ and stop. Run gh auth status; if not authenticated, tell the user to run gh auth login and stop.
Step 2: Locate the Seed
Seeds live in ~/.ouroboros/seeds/: interview Seeds as {seed_id}.yaml, PM Seeds as pm_seed_{id}.json. In priority order:
- An explicit
.yamlor.jsonpath argument. - The most recent files from
ls -t ~/.ouroboros/seeds/*.yaml ~/.ouroboros/seeds/*.json 2>/dev/null | head -5; if several exist, ask the user to choose. - A Seed path reported by
ooo seedorooo pmearlier in this conversation.
If none is found, tell the user to run ooo seed or ooo pm first, and stop.
Step 3: Parse the Seed
Detect the format by extension. Omit any section whose field is missing or empty rather than failing.
YAML Seed (ooo interview + ooo seed):
| Field | Use |
|---|---|
goal |
Epic title and Goal section |
constraints |
Constraints section |
acceptance_criteria |
Epic checklist, distributed to Task issues |
ontology_schema |
Ontology table (field, type, description) |
evaluation_principles |
Evaluation Principles table (name, weight, description) |
exit_conditions |
Exit Conditions (Definition of Done) |
metadata.ambiguity_score |
Confidence indicator |
metadata.seed_id |
Duplicate detection |
JSON PM Seed (ooo pm, PMSeed schema):
| Field | Use |
|---|---|
pm_id |
Duplicate detection |
product_name |
Epic title prefix |
goal |
Goal section |
constraints |
Constraints section |
success_criteria |
Acceptance Criteria checklist |
user_stories |
User Stories, each as "As a {persona}, I want to {action}, so that {benefit}." |
deferred_items |
Deferred Items section |
decide_later_items |
Open Questions section |
assumptions |
Assumptions section |
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.
- 6d ago Changed · -254 lines cb89a7443f76
- 1mo ago Changed · +10 lines d6469d708938
- 1mo ago First seen · 356 lines · 14 tokens per session scan A 159eddee8130
publish is a skill published in the GitHub repository Q00/ouroboros (6,258 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 1,541 once invoked, about $0.0001 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-30.
Other skills, from other repositories
client-onboarding
Use when a deal closed or a user signed up and the first 30 days need an activation plan: sales→delivery handoff, one verifiable activation event, kickoff, and a 30/60/90 or day-0→14 plan with owners, dates and a measurable exit. NOT reactive ticket triage (that is customer-support), NOT renewals/churn past the…
grants
Use when pursuing non-dilutive public or foundation funding — money you neither repay nor give equity for: finding a fit call, go/no-go, registration (UEI/PIC/BDNS), or writing the rubric-scored application, logic model, budget justification, or LOI. NOT an equity round (that is fundraising), NOT a paying-customer SOW…
procurement
Use when a small operator must choose what to buy and from whom: pick a supplier, write an RFI/RFQ/RFP that returns comparable bids, score quotes on total cost of ownership, negotiate price and payment terms, or judge single-source risk. NOT redlining the purchase agreement (that is contracts), NOT the price you…
proposals
Use when writing the document a buyer reads to say yes — a commercial proposal or Statement of Work, turning discovery notes into a scoped and priced document, adding tiers so the middle one wins, or diagnosing a proposal that will not close. NOT the binding legal agreement with its liability and IP clauses (that is…
project-ops
Use when an operator wants to run a small or mid-sized project from a flat file instead of standing up Jira or Asana — dated milestones each with one named owner and a binary done-test, rule-driven RAG status, a RAID log, slippage detection, and a two-minute weekly status report. NOT sequencing the engineering work…
ftd
Use for ordinary authorised change — the default lane once the decisor has ruled out a question and not selected the chain. Keeps one feature document per feature in 02-DOCS holding intent, scope, checklist, evidence and next step, checks tasks off only against observed proof, and asks whether to branch before the…