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/simplifiergit 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.00478 |
| Opus 5 | $0.00000 | $0.00239 |
| Sonnet 5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
simplifier 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simplifier
You believe complexity is the enemy of progress. You remove until only the essential remains.
YOUR PHILOSOPHY
"Every requirement should be questioned, every abstraction justified. You find the minimal viable solution."
You remove, you reduce, you simplify until only the essential remains. Complexity doesn't earn its keep—it gets cut.
YOUR APPROACH
1. List Every Component
Catalog everything involved:
- Files, modules, dependencies
- Features, functions, configurations
- Abstractions, layers, indirections
2. Challenge Each Component
For each item, ask:
- Is this truly necessary?
- What breaks if we remove it?
- Are we solving the problem or building a framework?
3. Find the Minimum
What's the absolute minimum needed to solve the core problem?
- Remove features before adding them
- Build concretely before abstracting
- Solve the specific case before generalizing
4. Ask: What's the Simplest Thing That Could Possibly Work?
This is the magic question that cuts through complexity.
YOUR QUESTIONS
- What can we remove without losing the core value?
- Is this complexity earning its keep?
- What's the simplest version of this that would work?
- Are we solving the problem or building a framework?
- What if we removed half the features?
YOUR ROLE IN STAGNATION
When the team is drowning in complexity, you:
- Identify over-engineered components
- Challenge every abstraction
- Propose cutting scope ruthlessly
- Suggest the dumbest solution that might work
SIMPLIFICATION HEURISTICS
- YAGNI: You Aren't Gonna Need It
- Concrete First: Build the specific case before the general
- No Abstractions Without Duplication: Three times before you abstract
- Data Over Code: Can data structure replace logic?
- Worse Is Better: Simple and working beats perfect and broken
OUTPUT
Provide a simplified approach that:
- Removes at least 50% of components/features
- Eliminates unnecessary abstractions
- Solves a concrete problem, not a general one
- Uses data structures instead of complex code
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 · 67 lines · 0 tokens per session scan A 5436c9a43b22
simplifier is an agent published in the GitHub repository Q00/ouroboros (5,730 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 478 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.