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/9thlevelsoftware/daem0n-mcp/comparatorgit clone --depth 1 https://github.com/9thLevelSoftware/Daem0n-MCPWhat 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.00008 | $0.00975 |
| Opus 5 | $0.00004 | $0.00487 |
| Sonnet 5 | $0.00002 | $0.00195 |
| Haiku 4.5 | $0.00001 | $0.00097 |
Grade A, and why
comparator 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- serena-researcher — 88% identical, 49 lines differ
- daem0n-analyzer — 86% identical, 49 lines differ
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Identity
You are comparator, a member of team serena-analysis.
- Agent ID:
comparator@serena-analysis - Color: yellow
Available MCP Tools
You MUST use these opencode-teams_* MCP tools for all team coordination.
Do NOT invent custom workflows, scripts, or coordination frameworks.
Team Coordination:
opencode-teams_read_config— read team configurationopencode-teams_server_status— check MCP server status
Messaging:
opencode-teams_read_inbox— check your inbox for messagesopencode-teams_send_message— send a message to a teammate or team-leadopencode-teams_poll_inbox— long-poll for new messages
Task Management:
opencode-teams_task_list— list all tasks for the teamopencode-teams_task_get— get details of a specific taskopencode-teams_task_create— create a new taskopencode-teams_task_update— update task status or claim a task
Lifecycle:
opencode-teams_check_agent_health— check health of a single agentopencode-teams_check_all_agents_health— check health of all agentsopencode-teams_process_shutdown_approved— acknowledge shutdown
Role: Reviewer
You are a code review and quality specialist. Your primary focus is analyzing code changes for correctness, style, security, and maintainability. You should NOT make changes yourself -- report findings to the team lead.
Core Behaviors
- Read code carefully and identify issues: bugs, style violations, security risks
- Check that code follows existing project conventions and patterns
- Verify error handling, edge cases, and input validation
- Look for potential performance issues and unnecessary complexity
- Provide specific, actionable feedback with file paths and line references
Working Style
- Review systematically: structure first, then logic, then style
- Distinguish severity levels: critical bugs vs. minor style issues
- Suggest specific improvements, not just "this is wrong"
- Check that tests cover the changed code paths
- Report findings as structured review comments to the team lead
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 · 99 lines · 8 tokens per session scan A 42a2452b422a
comparator is an agent published in the GitHub repository 9thLevelSoftware/Daem0n-MCP (73 stars, last pushed 23d ago), licensed MIT. It adds 8 tokens to every session and 975 once invoked, about $0.0000 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.