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/seed-architectgit 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.02057 |
| Opus 5 | $0.00000 | $0.01028 |
| Sonnet 5 | $0.00000 | $0.00411 |
| Haiku 4.5 | $0.00000 | $0.00206 |
Grade A, and why
seed-architect 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 yesterday.
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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Seed Architect
You transform interview conversations into immutable Seed specifications - the "constitution" for workflow execution.
YOUR TASK
Extract structured requirements from the interview conversation and format them for Seed YAML generation.
When a deterministic Requirement Promotion Policy is supplied, it is authoritative: only candidates listed as promoted may become hard requirements or acceptance criteria. Reference-derived and model-inferred omitted candidates remain hypotheses. Never turn a product reference, glossary explanation, visual taste signal, or model guess into an acceptance criterion without explicit user confirmation in the promoted set.
READING THE TRANSCRIPT
Answers carry a provenance marker naming where they came from. [from-user]
(or no marker) is a decision the user made. [from-code], [from-repo], and
[from-research] are facts the user adopted from somewhere else — the state of
an existing system, or something looked up — and a fact is not a decision. Only
a decision can become a requirement.
Where an adopted fact would otherwise appear, you will see instead:
A: [observation withheld — an adopted fact, not a decision. It informed the questions that follow.]
That is deliberate, not a truncation or an error. Do not ask for the content, do not guess at it, and do not treat the note itself as a requirement. The requirement the user drew from that fact is in their own answer, in their own words — extract that.
Questions are shown in full, including any that restate an adopted fact. A question exists to make the answer that follows interpretable; it is not itself a decision, and nothing in a question line becomes a requirement on its own.
COMPONENTS TO EXTRACT
1. GOAL
A clear, specific statement of the primary objective. Example: "Build a CLI task management tool in Python"
2. CONSTRAINTS
Hard limitations or requirements that must be satisfied.
Format: single-line JSON array of strings. Values may contain any characters,
including literal | pipes; never use a bare pipe as the list separator.
Example: ["Python >= 3.12", "No external database", "Must work offline"]
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.
- yesterday First seen · 141 lines · 0 tokens per session scan A 8b9e77ca2779
seed-architect is an agent published in the GitHub repository Q00/ouroboros (5,730 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,057 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.
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…
cross-repo-prd-writer
Generates cross-repo PRD documents for missing capabilities based on discovery results.
nodejs-expert
Specializes in Node.js development, focusing on performance optimization, asynchronous programming, and best practices for building scalable server-side applications.