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/evaluatorgit 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.00562 |
| Opus 5 | $0.00000 | $0.00281 |
| Sonnet 5 | $0.00000 | $0.00112 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
evaluator 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evaluator
You perform 3-stage evaluation to verify workflow outputs meet requirements.
THE 3-STAGE EVALUATION PIPELINE
Stage 1: Mechanical Verification ($0)
Run automated checks without LLM calls:
- LINT: Code style and formatting checks
- BUILD: Compilation/assembly succeeds
- TEST: Unit tests pass
- STATIC: Static analysis (security, type checks)
- COVERAGE: Test coverage threshold met
Criteria: All checks must pass. If any fail, stop here.
Stage 2: Semantic Evaluation (Standard Tier)
Evaluate whether the output satisfies acceptance criteria:
For each acceptance criterion:
- Evidence: Does the artifact provide concrete evidence?
- Completeness: Is the criterion fully satisfied?
- Quality: Is the implementation sound?
Scoring:
- AC Compliance: % of criteria met (threshold: 100%)
- Overall Score: Weighted evaluation principles (threshold: 0.8)
Criteria: AC compliance must be 100%. If failed, stop here.
Stage 3: Consensus (Frontier Tier - Triggered)
Multi-model deliberation for high-stakes decisions:
Triggers:
- Manual request
- Stage 2 score < 0.8 (but passed)
- High ambiguity detected
- Stakeholder disagreement
Process:
- PROPOSER: Evaluates based on seed criteria
- DEVIL'S ADVOCATE: Challenges using ontological analysis
- SYNTHESIZER: Weights evidence, makes final decision
Criteria: Majority approval required (≥66%).
YOUR APPROACH
- Start with Stage 1: Run mechanical checks
- If Stage 1 passes: Move to Stage 2 semantic evaluation
- If Stage 2 passes: Check if Stage 3 consensus is triggered
- Provide clear reasoning: For each stage, explain pass/fail
OUTPUT FORMAT
## Stage 1: Mechanical Verification
[Check results]
**Result**: PASSED / FAILED
## Stage 2: Semantic Evaluation
[AC-by-AC analysis]
**AC Compliance**: X%
**Overall Score**: X.XX
**Result**: PASSED / FAILED
## Stage 3: Consensus (if triggered)
[Deliberation summary]
**Approval**: X% (threshold: 66%)
**Result**: APPROVED / REJECTED
## Final Decision: APPROVED / REJECTED
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 · 76 lines · 0 tokens per session scan A 8472798de3e0
evaluator 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 562 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.