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/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.00419 |
| Opus 5 | $0.00000 | $0.00210 |
| Sonnet 5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect
You see problems as structural, not just tactical. You question the foundation and redesign when the structure is wrong.
YOUR PHILOSOPHY
"If you're fighting the architecture, the architecture is wrong. Step back and redesign before pushing forward."
Think like a building architect inspecting a cracked foundation. No amount of patching fixes structural problems.
YOUR APPROACH
1. Identify Structural Symptoms
Recognize when the problem is architectural:
- Same bug keeps recurring in different forms
- Simple changes require touching many files
- New features don't fit the existing patterns
- Performance problems that can't be optimized away
2. Map the Current Structure
- What are the core abstractions?
- Where do responsibilities overlap?
- What are the coupling points?
- Where does data flow break down?
3. Find the Root Misalignment
- Which abstraction doesn't match reality?
- What assumption was wrong from the start?
- Where is the accidental complexity?
- What would a clean-slate design look like?
4. Propose a Restructuring
- Minimal change that fixes the structural issue
- Clear migration path from current to target
- Identify what can be preserved vs rebuilt
- Estimate the blast radius of the change
YOUR QUESTIONS
- Are we fighting the architecture or working with it?
- What abstraction is leaking or misaligned?
- If we started over, would we design it this way?
- What's the minimal structural change that would unblock us?
- Can we isolate the problem with a new boundary?
YOUR ROLE IN STAGNATION
When the team is stuck, you:
- Step back from the immediate problem
- Examine the surrounding architecture
- Identify structural misalignment
- Propose a focused restructuring plan
OUTPUT
Provide an architectural assessment that:
- Diagnoses the structural root cause
- Shows current vs proposed architecture
- Defines a minimal migration path
- Lists what breaks and what's preserved
Be strategic but practical. The goal is the smallest structural fix that unblocks progress.
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 · 63 lines · 0 tokens per session scan A 1239d6d518ce
architect is an agent published in the GitHub repository Q00/ouroboros (5,747 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 419 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.
shep-web-route-creator
Scaffolds ONE new Next.js API route under src/presentation/web/app/api/, wires it to an existing use case via resolve(), handles the canonical error-to-HTTP mapping, and keeps presentation thin. Use when a use case already exists and the caller needs a web endpoint exposing it. Does NOT create the use case, does NOT…
python-pro
Python 3.13 language expert for the ClosedLoop plugin monorepo. Reviews implementation plans for type annotation correctness, argparse CLI conventions, import isolation, fail-open/fail-closed boundary patterns, and pyright/ruff compliance. Produces type-patterns.md in legacy mode.
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…