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/evangelosmeklis/thufirWrote 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/commands/evangelosmeklis/thufir/investigate)<a href="https://agentmods.dev/commands/evangelosmeklis/thufir/investigate"><img src="https://agentmods.dev/badge/commands/evangelosmeklis/thufir/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/commands/evangelosmeklis/thufir/investigate"><img src="https://agentmods.dev/badge/commands/evangelosmeklis/thufir/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.00011 | $0.01940 |
| Opus 5 | $0.00005 | $0.00970 |
| Sonnet 5 | $0.00002 | $0.00388 |
| Haiku 4.5 | $0.00001 | $0.00194 |
Grade A, and why
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 10d 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 — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interactive RCA Investigation Command
Purpose
Guide users through a comprehensive root cause analysis investigation via an interactive wizard. This command is flexible and works for any type of production incident, whether from Prometheus, GitHub, GitLab, or manual investigation.
Instructions for Claude
When this command is invoked, guide the user through a systematic RCA investigation:
Step 1: Gather Initial Information
Use AskUserQuestion to collect incident details:
Question 1: Incident Source Ask: "How did you learn about this incident?" Options:
- "Prometheus alert"
- "GitHub issue"
- "GitLab issue"
- "Manual detection (user report, logs, etc.)"
Based on answer, branch:
- If Prometheus: Delegate to
/rca:analyze-prometheuscommand - If GitHub: Delegate to
/rca:analyze-githubcommand - If GitLab: Delegate to
/rca:analyze-gitlabcommand - If Manual: Continue with questions below
Question 2: Basic Incident Info (for manual investigations) Ask user to provide:
- "What is the problem? (Brief description)"
- "When did it start? (Timestamp or approximate time)"
- "Is it still occurring?"
Question 3: Symptoms Ask: "What symptoms are you seeing?" Allow multi-select or free text:
- Error messages
- Performance degradation
- Service unavailability
- Data inconsistency
- Other (specify)
Question 4: Impact Ask: "How severe is the impact?" Options:
- "Critical - Major user impact"
- "High - Significant user impact"
- "Medium - Some users affected"
- "Low - Minor or no user impact"
Step 2: Collect Error Details
Ask user for specific error information:
Error Messages:
- "Please paste any error messages, stack traces, or relevant logs"
- Parse and extract:
- Error names
- Stack traces (file paths and line numbers)
- Error codes
- Timestamps
Affected Components:
- "Which service, feature, or component is affected?"
- "Which API endpoints or pages are failing?"
Scope:
- "Is this affecting all users or specific segments?"
- "Are specific geographic regions affected?"
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.
- 10d ago First seen · 312 lines · 11 tokens per session scan A 948d9164c796
investigate is a command published in the GitHub repository evangelosmeklis/thufir (7 stars, last pushed 8mo ago), licensed MIT. It adds 11 tokens to every session and 1,940 once invoked, about $0.0001 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 commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.