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.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.1 | $0.00014 | $0.02866 |
| Opus 5 | $0.00007 | $0.01433 |
| Sonnet 5 | $0.00003 | $0.00573 |
| Haiku 4.5 | $0.00001 | $0.00287 |
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 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 — 366 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ouroboros:publish
Convert a Seed specification into structured GitHub Issues for team workflows.
Usage
ooo publish [seed_path]
/ouroboros:publish [seed_path]
Trigger keywords: "publish to github", "create issues from seed", "seed to issues"
Instructions
When the user invokes this skill:
Step 1: Prerequisite Check
1a. Verify gh CLI is installed:
command -v gh >/dev/null 2>&1 && echo "OK" || echo "MISSING"
If missing, tell the user:
GitHub CLI (gh) is not installed.
Install it: https://cli.github.com/
Stop.
1b. Verify gh is authenticated:
gh auth status
If not authenticated, tell the user:
GitHub CLI is not authenticated. Run: gh auth login
Stop.
Step 2: Locate the Seed
Ouroboros stores seeds in ~/.ouroboros/seeds/:
- Interview seeds:
~/.ouroboros/seeds/{seed_id}.yaml(YAML) - PM seeds:
~/.ouroboros/seeds/pm_seed_{id}.json(JSON)
Determine the Seed source in this priority order:
- Explicit path argument: If the user provided a file path (
.yamlor.json), read it directly - Most recent seed file: Search for the most recent seed in the standard location:
If multiple seeds exist, present the top candidates via AskUserQuestion and let the user choose.ls -t ~/.ouroboros/seeds/*.yaml ~/.ouroboros/seeds/*.json 2>/dev/null | head -5 - Conversation context: If
ooo seedorooo pmwas just run in this conversation and the seed path was reported, use that path.
If no seed is found:
No Seed found. Run `ooo seed` or `ooo pm` first to generate a specification.
Stop.
Step 3: Parse the Seed
Detect the file format by extension and parse accordingly:
For YAML seeds (from ooo interview + ooo seed):
Read the YAML file and extract:
goal→ Epic title and descriptionconstraints→ Listed in Epic bodyacceptance_criteria→ Checklist items in Epic + distributed to Task issuesontology_schema→ Documentation section in Epicevaluation_principles→ Quality criteria referenceexit_conditions→ Definition of Donemetadata.ambiguity_score→ Confidence indicatormetadata.seed_id→ Used for duplicate detection
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 Changed · +10 lines d6469d708938
- 7d ago First seen · 356 lines · 14 tokens per session scan A 159eddee8130
publish is a skill published in the GitHub repository Q00/ouroboros (5,777 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 2,866 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
prd
A guide for writing a PRD, or Product Requirements Document, which explains what a product or feature should achieve and who it is for. It covers goals, users, success measures, limits, prior work, and excluded scope.
product-discovery
Product discovery workflow with OST, assumption testing, and interview scripts.
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…
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…
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…