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 dorayo/orchestrix-skills --skill investigategit clone --depth 1 https://github.com/dorayo/orchestrix-skillsWrote 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/dorayo/orchestrix-skills/investigate)<a href="https://agentmods.dev/skills/dorayo/orchestrix-skills/investigate"><img src="https://agentmods.dev/badge/skills/dorayo/orchestrix-skills/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/dorayo/orchestrix-skills/investigate"><img src="https://agentmods.dev/badge/skills/dorayo/orchestrix-skills/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.00033 | $0.00887 |
| Opus 5 | $0.00016 | $0.00443 |
| Sonnet 5 | $0.00007 | $0.00177 |
| Haiku 4.5 | $0.00003 | $0.00089 |
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 7d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Investigate (Root Cause Before Any Fix)
Debugging is not "try changes until it passes". It is locating the mechanism.
Core principle: A fix you cannot explain mechanistically is not a fix — it is a coincidence that will regress.
The Iron Law
NO FIX WITHOUT A ROOT CAUSE STATED AS:
"X happens BECAUSE Y — evidenced by Z (something I observed this session)"
Process
- Reproduce. Find the exact command/steps that show the symptom, run them, capture the output verbatim. Read the error LITERALLY — the message usually says what is wrong, not what you assume is wrong. Cannot reproduce → that IS the finding (report the conditions tried; do not "fix" what you cannot see).
- Localize. Shrink the search space with evidence, not intuition:
git log/git bisectwhen it used to work — what changed?- Binary-search the pipeline: add temporary instrumentation (prints/asserts) at midpoints to find where good state becomes bad state.
- Minimize the reproduction — smallest input that still fails.
- Hypothesize and FALSIFY. For each hypothesis, design the observation that would DISPROVE it, then run it. A hypothesis you only sought confirmation for is not tested. Two failed rounds on the same theory → the bug is in an assumption one level deeper (the config, the framework contract, the data, the environment) — widen, don't re-try harder.
- State the root cause in the iron-law form, plus:
- the minimal fix scope (which file/function, what change class),
- the regression test that would have caught it,
- any OTHER symptoms this mechanism predicts (check them — a mechanism that doesn't explain all symptoms is incomplete).
- Revert your instrumentation.
git diffmust be clean when you finish.
Output: root_cause_report
# Root cause — <symptom, one line>
## Reproduction — exact command; fails with <output tail>.
## Mechanism — X happens because Y. Evidence: Z (file:line / captured output).
## Fix scope — <file(s)>, <change class>. Explicitly NOT needed: <what a shotgun fix would have touched>.
## Regression test — <the test to add so this cannot silently return>.
## Ruled out — <hypotheses falsified and how> (saves the next person re-walking them).
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.
- 7d ago Changed · +1 lines af76adf4a92d
- 11d ago First seen · 83 lines · 33 tokens per session scan A 076cc03e53cc
investigate is a skill published in the GitHub repository dorayo/orchestrix-skills (2 stars, last pushed 9d ago), licensed MIT. It adds 33 tokens to every session and 887 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.