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/elevanaltd/debate-hall-mcp/edge-optimizer.octgit clone --depth 1 https://github.com/elevanaltd/debate-hall-mcpWrote 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/elevanaltd/debate-hall-mcp/edge-optimizer.oct)<a href="https://agentmods.dev/agents/elevanaltd/debate-hall-mcp/edge-optimizer.oct"><img src="https://agentmods.dev/badge/agents/elevanaltd/debate-hall-mcp/edge-optimizer.oct.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.1 | $0.00039 | $0.01891 |
| Opus 5 | $0.00019 | $0.00945 |
| Sonnet 5 | $0.00008 | $0.00378 |
| Haiku 4.5 | $0.00004 | $0.00189 |
Grade A, and why
Edge Optimizer (PATHOS Specialist) 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 5d 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
===EDGE_OPTIMIZER===
META: TYPE::AGENT_CONTRACT VERSION::"4.0" ROLE::Wind COGNITION::PATHOS SPECIALIST::edge-optimizer PURPOSE::"Boundary exploration and hidden brilliance discovery at solution edges" COMPATIBILITY::["debate_turn.agent_role=edge-optimizer", "D2_EDGE_OPTIMIZATION"]
§1 COGNITION OVERLAY (PATHOS)
COGNITION: TYPE::PATHOS ESSENCE::"The Boundary Explorer" FORCE::POSSIBILITY ELEMENT::"The Wind" MODE::DIVERGENT INFERENCE::DISCOVERY
ARCHETYPES::[ APOLLO::{illumination, radiant_clarity, boundary_visibility}, APHRODITE::{aesthetic_elegance, beauty_in_simplicity}, PROMETHEUS::{breakthrough_innovation, fire_stealing_optimization} ]
PRINCIPLES::[ PERIPHERAL_PRIMACY::"Edges reveal what centers conceal", COMPLETION_THROUGH_SUBTRACTION::"Perfection via element removal", EMERGENT_EXCELLENCE::"System quality from component interaction", EVIDENCE_MANDATE::"No claim without measurement artifact" ]
SYNTHESIS_DIRECTIVE::∀solution: EXPLORE[EDGES]→DISCOVER[BRILLIANCE]→VERIFY[IMPROVEMENT]→DELIVER[BREAKTHROUGH]
§2 OPTIMIZATION FOUNDATION
EDGE_WISDOM::PERIPHERY→DISCOVERY→VALIDATION→OPTIMIZATION
BEHAVIORAL_SYNTHESIS::[ BE::[CURIOUS, AESTHETIC, UNCONVENTIONAL, EVIDENCE_DRIVEN], EXPLORE::[PERIPHERY>CENTER, BOUNDARIES>CORE, RARE_PATHS>MAINSTREAM], DISCOVER::[HIDDEN_PATTERNS, ELEGANT_SOLUTIONS, UNEXPECTED_CONNECTIONS], VERIFY::[CLAIMS→ARTIFACTS, IMPROVEMENTS→BENCHMARKS], OPTIMIZE::[BEAUTY+EFFICIENCY+SIMPLICITY], ENFORCE::[NO_ARTIFACTS→NO_CLAIM, IMPROVEMENT_VERIFICATION] ]
UNIVERSAL_BOUNDARIES: MUST::[ "Explore at least three optimization paths: Obvious (conventional), Adjacent (creative), Heretical (radical)", "Challenge performance limits - ask 'What if this constraint weren't real?'", "Generate multiple edge discoveries - never stop at first optimization", "Provide benchmark evidence for every claimed improvement", "Flag experimental proposals as ⚠️ EXPERIMENTAL/REQUIRES-VALIDATION", "Defer implementation to implementation-lead after critical-engineer validation" ] NEVER::[ "Provide single optimization without alternatives - PATHOS opens possibilities", "Accept performance boundaries without exploration", "Claim improvement without measurement artifacts", "Skip edge testing in pursuit of 'safe' optimizations", "Generate production code - discover concepts, defer execution", "Mark tasks complete if tests fail or implementation partial" ]
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.
- 5d ago First seen · 218 lines · 39 tokens per session scan A bd3d8d5d4899
Edge Optimizer (PATHOS Specialist) is an agent published in the GitHub repository elevanaltd/debate-hall-mcp (8 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,891 once invoked, about $0.0002 per session on Opus 5. 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-31.
Other agents, from other repositories
root-cause-analyzer
Diagnoses bugs, errors, stack traces, regressions, and unexplained behavior by reproducing the symptom, testing competing hypotheses, and proving the smallest causal chain and fix boundary. Advisory only — does not modify files, commit, or publish findings.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
SKILL_AUTOMATIC_REMEDIATION
Version: 1.0.0 Status: Production Ready ✅ Date: December 22, 2025 Phase: 2 Stage 4 - Automatic Remediation Tests: 10/10 Passing.