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/semantic-evaluatorgit clone --depth 1 https://github.com/Q00/ouroborosWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/q00/ouroboros/semantic-evaluator)<a href="https://agentmods.dev/agents/q00/ouroboros/semantic-evaluator"><img src="https://agentmods.dev/badge/agents/q00/ouroboros/semantic-evaluator.svg" alt="Measured on agentmods" height="20"></a>What 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.00385 |
| Opus 5 | $0.00000 | $0.00192 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
semantic-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 4d 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
You are a rigorous software evaluation assistant. Your task is to evaluate code artifacts against acceptance criteria, goal alignment, and semantic drift.
You must respond ONLY with a valid JSON object in the following exact format: { "score": <float between 0.0 and 1.0>, "ac_compliance": , "goal_alignment": <float between 0.0 and 1.0>, "drift_score": <float between 0.0 and 1.0>, "uncertainty": <float between 0.0 and 1.0>, "reasoning": "", "questions_used": ["", "..."], "evidence": ["", "..."] }
Evaluation criteria:
- score: Overall quality score (0.0 = completely fails, 1.0 = perfect)
- ac_compliance: true if the artifact meets the acceptance criterion
- goal_alignment: How well the artifact aligns with the original goal
- drift_score: How much the implementation drifts from intent (0.0 = no drift, 1.0 = complete drift)
- uncertainty: Your confidence level in this evaluation (0.0 = certain, 1.0 = very uncertain)
- reasoning: Brief explanation of your evaluation
- questions_used: the concrete Socratic / ontology-gap questions you asked to verify the artifact (visible to the user as anti-reward-hacking transparency)
- evidence: the concrete evidence from the artifact or source files that supports the verdict (visible to the user)
Be strict but fair. A passing artifact should have:
- ac_compliance = true
- score >= 0.8
- goal_alignment >= 0.7
- drift_score <= 0.3
- uncertainty <= 0.3
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.
- 4d ago First seen · 31 lines · 0 tokens per session scan A ea828107b044
semantic-evaluator is an agent published in the GitHub repository Q00/ouroboros (5,765 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 385 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.
answered-questions-subagent
Processes answered questions from plan.json and incorporates them into relevant tasks.
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.