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 agentmods add skills/q00/ouroboros/brownfieldnpx skills add Q00/ouroboros --skill brownfieldgit 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/brownfield)<a href="https://agentmods.dev/skills/q00/ouroboros/brownfield"><img src="https://agentmods.dev/badge/skills/q00/ouroboros/brownfield.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.02144 |
| Opus 5 | $0.00007 | $0.01072 |
| Sonnet 5 | $0.00003 | $0.00429 |
| Haiku 4.5 | $0.00001 | $0.00214 |
Grade A, and why
brownfield 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 3d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ouroboros:brownfield
Scan a root directory for existing git repositories and linked worktrees, then manage default repos used as context in interviews.
Usage
ooo brownfield # Scan repos and set defaults
ooo brownfield scan # Scan only (no default selection)
ooo brownfield defaults # Show current defaults
ooo brownfield set 6,18,19 # Set defaults by repo numbers
ooo brownfield detect [path] # Author mechanical.toml via one AI call
Trigger keywords: "brownfield", "scan repos", "default repos", "brownfield scan", "mechanical detect"
How It Works
Default flow (ooo brownfield with no args)
Step 1: Scan
Show scanning indicator:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Scanning for Existing Projects...
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Looking for git repositories and worktrees up to two directories below the scan root.
Local repos and repos with any remote name are eligible.
This may take a moment...
Implementation — use MCP tools only, do NOT use CLI or Python scripts:
CRITICAL — deferred-schema guard (prevents "Invalid tool parameters"):
This skill can call ouroboros_brownfield across multiple turns (scan,
set_defaults, defaults, and set). A deferred schema loaded for one turn is
NOT guaranteed to remain loaded for the next. Immediately before EVERY
ouroboros_brownfield call, re-run tool discovery query: "+ouroboros brownfield"
(idempotent — a no-op when already loaded). If the load returns no matching tool (and the tool is not already callable — an empty load for an already-exposed tool is an expected no-op, not absence),
stop with the MCP-not-available message instead of retrying the failing call.
- Load the brownfield MCP tool:
tool discovery query: "+ouroboros brownfield" - Call scan+register:
This walksTool: ouroboros_brownfield Arguments: { "action": "scan" }scan_root(up to two directory levels deep) for valid seed repos/worktrees and registers them in DB. Each repo or worktree found directly by the walk is registered self-only — Git worktree families are not expanded, so worktrees outside the depth-bounded walk (e.g. under.ouroboros/worktrees) are not pulled in. Existing defaults are preserved.
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.
- 3d ago Changed · +17 lines 9c9477269fdd
- 6d ago First seen · 225 lines · 14 tokens per session scan A 5dadce6a6116
brownfield is a skill published in the GitHub repository Q00/ouroboros (5,769 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 2,144 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
llm-pipeline
Use when wiring several LLM calls into a production flow: typed contracts between steps, a router/gateway so 429s, timeouts and outages fail over instead of taking you down, and cost control via caching, model tiers and abort caps. NOT single-prompt wording (that is prompt-engineering), NOT a model-driven tool loop…
worker-integration
Worker-Agent integration for intelligent task dispatch and performance tracking.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.