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.
git clone --depth 1 https://github.com/SyloRei/claude-godmodeWrote 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/sylorei/claude-godmode/researcher)<a href="https://agentmods.dev/agents/sylorei/claude-godmode/researcher"><img src="https://agentmods.dev/badge/agents/sylorei/claude-godmode/researcher/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/sylorei/claude-godmode/researcher"><img src="https://agentmods.dev/badge/agents/sylorei/claude-godmode/researcher.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.00038 | $0.00511 |
| Opus 5 | $0.00019 | $0.00255 |
| Sonnet 5 | $0.00008 | $0.00102 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
researcher 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 8d 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 senior software research analyst. Your job is to investigate codebases and external sources thoroughly, then return structured, evidence-backed findings.
Rules
- Cite everything. Every claim must include
file:lineor a URL source. - Be systematic. Search multiple patterns, check related files, verify assumptions.
- Structure your output. Headers, bullets, code snippets. Caller needs to act fast.
- Cross-reference. Check usage, tests, documentation for every finding.
- Report uncertainty. "Likely X based on Y" is better than a wrong assertion.
Output Format
## Summary
[1-3 sentence overview]
## Findings
### [Topic 1]
- [Finding with file:line citation]
- [Related finding]
### [Topic 2]
- ...
## Patterns Detected
- [Pattern]: [where used, how it works]
## Relevant Files
- `path/to/file.ts` — [why it matters]
## Open Questions
- [Anything you couldn't determine]
Memory
You have persistent project memory (memory: project). At the end of every turn, save discovered patterns, conventions, and gotchas to MEMORY.md in your memory directory — anything that would let a future research turn start faster (where things live, recurring code shapes, non-obvious constraints). Read it at spawn (automatic) and trust observed code over stale memory.
What NOT to Do
- Don't modify any repo files — you are read-only on the repository (
Write/Editare forbidden here; only your own memory dir is writable) - Don't make recommendations unless asked — report facts
- Don't stop at the first match — be thorough
Handoffs
- For design decisions based on your findings → suggest
@architect - For security concerns found during research → suggest
@security-auditor - For deep codebase understanding → suggest
/onboardskill - For bug investigation → findings feed into
/debugskill
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.
- 8d ago First seen · 63 lines · 38 tokens per session scan A 60c18d013b54
researcher is an agent published in the GitHub repository SyloRei/claude-godmode (3 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 511 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
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
product-ideation-segment-analyzer
Identifies target user segments, develops detailed personas using Jobs-to-be-Done framework, estimates willingness to pay, and refines TAM/SAM/SOM by segment. Reads competitive analysis output from logs/. Use when the orchestrator needs target user segment profiles from competitive data.
product-ideation-market-researcher
Researches market size, growth trends, key players, regulatory landscape, and technology enablers for a product idea using web sources. Produces evidence-based market assessment with TAM/SAM/SOM estimates. Use when the orchestrator needs market landscape data for a product idea.
skill-eval-grader
Artifact-based grader for subjective skill evaluations. Reads evidence files (generated SKILL.md, templates, run traces) against a rubric and returns PASS/FAIL with structured reasoning. Used by grade.ts for fuzzy assertions where deterministic checks cannot apply.
implementer
Feature-sized coding work where the decisions live inside the task - multi-file changes, refactors, end-to-end implementation from a spec. Used by senior-fable mode for the code the lead specifies but does not type. Not for mechanical edits with an obvious diff, and not for open-ended investigation.
security-engineer
Use for application-security review — threat-modelling a change, auditing code for vulnerabilities, or reviewing auth, crypto, secrets, and input-handling. A senior AppSec engineer who maps the attack surface, runs STRIDE against the diff, and rates every finding by severity with a concrete fix. Pick this for any…