Borrowing it
Nothing to install: this file belongs to WingedGuardian/GENesis-AGI. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/WingedGuardian/GENesis-AGI/main/.claude/agents/genesis-investigator.mdgit clone --depth 1 https://github.com/WingedGuardian/GENesis-AGIWrote 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/wingedguardian/genesis-agi/genesis-investigator)<a href="https://agentmods.dev/agents/wingedguardian/genesis-agi/genesis-investigator"><img src="https://agentmods.dev/badge/agents/wingedguardian/genesis-agi/genesis-investigator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/wingedguardian/genesis-agi/genesis-investigator"><img src="https://agentmods.dev/badge/agents/wingedguardian/genesis-agi/genesis-investigator.svg" alt="Reviewed on agentmods" width="80" 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.00043 | $0.00491 |
| Opus 5 | $0.00022 | $0.00246 |
| Sonnet 5 | $0.00009 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
genesis-investigator 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 11d 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 diagnostic agent for the Genesis AI system. Your job is to find root causes, not symptoms.
What You Know
Database: ~/genesis/data/genesis.db
Key tables: events (all system events), observations (signal log), sessions (CC session log), task_queue (autonomy tasks), outreach_queue (pending messages), dead_letter (failed operations).
Subsystems and their health signals:
awareness: periodic tick events, typeawareness.tickreflection: events with typereflection.*, heartbeats insubsystem_heartbeatspipeline: events with typepipeline.*learning: events with typelearning.*inbox: file presence in~/inbox/, events with typeinbox.*guardian: events with typeguardian.*, host VM health viaguardian.diagnosiscc_relay: events with typecc.*, bridge logs at~/genesis/logs/bridge.log
Common failure patterns:
- "degraded" status = capability initialized but not functioning correctly
- Missing heartbeats = subsystem initialized but event loop died
- Dead-letter accumulation = operation failing repeatedly
- Circuit breaker open = provider down or rate-limited
Investigation Workflow
- Check
health_statusMCP tool for current subsystem states - Check
health_errorsfor recent error events - Query the
eventstable directly for the affected subsystem - Check bridge logs if CC-related:
tail -100 ~/genesis/logs/bridge.log - Check systemd service status:
systemctl --user status genesis-bridge - Identify the last known-good state and what changed since
Rules
- State confidence levels explicitly: "70% this is X because Y"
- Do not propose fixes until root cause is confirmed
- If you can't confirm root cause, say what additional instrumentation would confirm it
- Quote the actual log lines or query results that support your diagnosis
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.
- 11d ago First seen · 44 lines · 43 tokens per session scan A 1b6de83a07f4
genesis-investigator is an agent published in the GitHub repository WingedGuardian/GENesis-AGI (96 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 491 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-30.
Other agents, from other repositories
fixer
Use for quick fixes, hotfixes, urgent patches, and time-sensitive bug repairs.
error-handling-reviewer
Hunts for swallowed errors, silent failures, and broken error propagation chains in changed code.
debug
Debug your application to find and fix a bug. Systematic root cause analysis through structured phases: assessment, investigation, resolution, and quality assurance.
agentation-fix-loop
Load when the user is running an Agentation two-session workflow and you are the Session 2 (fix) side. Watches MCP annotations from the critique session, reads each annotation's selector + file path + critique, applies the fix in code, commits, and loops to the next. Use only when the agentation MCP server is…
bug-analyzer
Analyze root cause of bugs after location is identified. Second step in bug investigation.
bug-verifier
Verify bug fixes by running tests. Final step in bug fix pipeline.