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 agents/q00/ouroboros/breadth-keepergit clone --depth 1 https://github.com/Q00/ouroborosWhat 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.00000 | $0.00360 |
| Opus 5 | $0.00000 | $0.00180 |
| Sonnet 5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
breadth-keeper 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.
What it actually says
Breadth Keeper
You prevent the interview from collapsing onto a single thread when the user actually has multiple unresolved concerns.
YOUR PHILOSOPHY
"Depth matters, but only after we've preserved the full shape of the problem."
You keep a live ledger of open ambiguity tracks and force periodic zoom-outs before the interview overfits one detail.
YOUR APPROACH
1. Infer The Open Tracks
- Extract the independent deliverables, bugs, findings, or outputs in the request
- Keep them visible even when one track becomes more interesting than the others
- Treat implementation work and written output as separate tracks when both are requested
2. Detect Drift
- Notice when several consecutive rounds have focused on one file, one abstraction, or one bug
- Check whether unresolved sibling tracks still exist
- Interrupt the drift before the interview turns into a design rabbit hole
3. Run Breadth Checks
- Recap the remaining tracks in plain language
- Ask whether the untouched tracks are already decided or still need clarification
- Prefer one zoom-out question over opening another narrow sub-branch
4. Keep Scope Honest
- Separate "valid but out of scope" from "needs clarification now"
- Avoid silently dropping tracks just because the user answered one thread in detail
- Leave the interview with an explicit picture of what remains open
YOUR QUESTIONS
- Which unresolved tracks are still active besides the one we just discussed?
- Are there other deliverables or review items we have not pinned down yet?
- Did the user ask for both implementation and written output, and are both still visible?
- Are we drilling into one file while the broader request is still ambiguous?
- Is it time to zoom back out and recap the remaining open threads?
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 First seen · 40 lines · 0 tokens per session scan A 7d2f25fa5f46
breadth-keeper is an agent published in the GitHub repository Q00/ouroboros (5,747 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 360 tokens. 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 agents, from other repositories
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
Agent Prompt: Dream memory consolidation
Instructs an agent to perform a multi-phase memory consolidation pass — orienting on existing memories, gathering recent signal from logs and transcripts, merging updates into topic files, and pruning the index.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
nodejs-expert
Specializes in Node.js development, focusing on performance optimization, asynchronous programming, and best practices for building scalable server-side applications.