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 skills add rp1-run/rp1 --skill code-investigategit clone --depth 1 https://github.com/rp1-run/rp1Wrote 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/skills/rp1-run/rp1/code-investigate)<a href="https://agentmods.dev/skills/rp1-run/rp1/code-investigate"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/code-investigate/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/skills/rp1-run/rp1/code-investigate"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/code-investigate.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.00031 | $0.00831 |
| Opus 5 | $0.00015 | $0.00415 |
| Sonnet 5 | $0.00006 | $0.00166 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
code-investigate 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 yesterday.
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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Root Cause Investigator
This command invokes the bug-investigator sub-agent for systematic issue analysis of the provided problem statement.
Before invoking the sub-agent or registering artifacts, derive EFFECTIVE_ISSUE_ID:
- If
ISSUE_IDis non-empty, use it unchanged. - Otherwise derive a deterministic lowercase kebab-case slug from
PROBLEM_STATEMENT. - Collapse repeated separators, trim leading/trailing
-, and if the slug would be empty useinvestigation.
Use EFFECTIVE_ISSUE_ID consistently for workspace paths, report paths, and agent inputs.
First emit: Generate RUN_ID as a UUID. Derive RUN_NAME from the problem statement: a brief summary (max 60 chars) prefixed with "Investigate: ".
On session start, emit the status change:
rp1 agent-tools emit \
--workflow code-investigate \
--type status_change \
--run-id {RUN_ID} \
--name "Investigate: {brief summary}" \
--step investigating \
--data '{"status": "running"}'
STATE-MACHINE
stateDiagram-v2
[*] --> investigating
investigating --> [*] : done
Invoke the bug-investigator agent with the freeform problem statement and derived issue id:
{% dispatch_agent "rp1-dev:bug-investigator" %} PROBLEM_STATEMENT={PROBLEM_STATEMENT}, ISSUE_ID={EFFECTIVE_ISSUE_ID}, KB_ROOT={kbRoot}, WORK_ROOT={workRoot} {% enddispatch_agent %}
The agent will:
- Analyze problem statement and gather context
- Form and test hypotheses systematically
- Add temporary debugging (tracked and reverted)
- Trace code execution paths
- Identify root cause with evidence
- Generate comprehensive investigation report
- Propose solutions with effort estimates
- Report back with findings
Emit btw_update events for key findings during the investigation:
rp1 agent-tools emit \
--workflow code-investigate \
--type btw_update \
--run-id {RUN_ID} \
--data '{"message": "{finding summary}"}'
After the agent writes the investigation report, register it as an artifact:
rp1 agent-tools emit \
--workflow code-investigate \
--type artifact_registered \
--run-id {RUN_ID} \
--step investigating \
--data '{"path": "issues/{EFFECTIVE_ISSUE_ID}/investigation_report.md", "storageRoot": "work_dir", "format": "markdown"}'
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.
- yesterday First seen · 108 lines · 31 tokens per session scan A d0c90d07f08d
code-investigate is a skill published in the GitHub repository rp1-run/rp1 (38 stars, last pushed yesterday), licensed Apache-2.0. It adds 31 tokens to every session and 831 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-09-07.
Other skills, from other repositories
error-translator
A Chinese-language assistant that translates English programming errors and explains what they mean. It covers common errors from languages and frameworks including Python, JavaScript, TypeScript, Java, and others.
eslint-fix
A project-aware assistant for finding and fixing ESLint errors, warnings, and configuration compatibility problems. ESLint is a tool that checks JavaScript and TypeScript code for style and common mistakes.
perf-profiler
A performance investigation guide that uses repeatable measurements and profiling evidence to find where software spends time or resources. Profiling records runtime activity such as CPU use, memory use, database work, or network delays.
log-analyzer
A log-analysis helper that reads application and system logs to find unusual patterns and likely causes. Logs are records of events such as errors, requests, warnings, and service activity.
fix
Dispatch fix subagent for FIX-FIRST gaps from review, re-review, then diagnose unresolved failures after 2 loops.
report
Investigate bugs comprehensively — cascade through trace, capture browser evidence, extract observability data, and prepare or explicitly create a GitHub issue with grounded findings.