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 mthines/agent-skills --skill holistic-analysisgit clone --depth 1 https://github.com/mthines/agent-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/mthines/agent-skills/holistic-analysis)<a href="https://agentmods.dev/skills/mthines/agent-skills/holistic-analysis"><img src="https://agentmods.dev/badge/skills/mthines/agent-skills/holistic-analysis.svg" alt="Measured on agentmods" 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.00224 | $0.04274 |
| Opus 5 | $0.00112 | $0.02137 |
| Sonnet 5 | $0.00045 | $0.00855 |
| Haiku 4.5 | $0.00022 | $0.00427 |
Grade A, and why
holistic-analysis 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 — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Holistic Analysis
When this skill activates, STOP all incremental patching. Do not attempt another narrow change. Instead, execute the full analysis protocol below before writing any code.
Contents
- Mode Detection — pick
fix(default),refactor, orreview(rule file) - Context Gathering — 11-point checklist before reasoning
- Call-Graph Map (optional accelerator) — mechanically seed the execution map when a call-graph CLI is available
- Phase 1: Full Execution Path Walkthrough — entry-to-exit map, per-block analysis, contract boundaries, summary
- Phase 2: Step Back — Identify the Principle
- Phase 3: Scene Set — Explain the Situation to the Duck
- Phase 4: Structured Hypothesis Generation — fix-mode root causes / refactor-mode approaches
- Phase 5: Meta-Cognitive Check — Challenge Your Own Reasoning
- Phase 6: Confidence Gate — Analysis Validation —
/confidence analysisor/confidence plan - Phase 7: Plan the Change — Words Before Code
- Phase 8: Implement and Verify —
/confidence codegate - Output Format
- Contribute verified facts to codebase-knowledge — writer-primary, best-effort, gated on real verification
- Anti-Patterns — What NOT to Do
Mode Detection
Check $ARGUMENTS for mode:
| Mode | Default | Use case |
|---|---|---|
fix |
yes | Bug, broken behavior, failing test — something is wrong and needs root cause analysis |
refactor |
Restructuring, cleanup, improvement — the code works but needs to be better | |
review |
PR validation — does this diff implement what its description claims, and does the change make sense given how the changed code is used in the wider system? Returns structured findings for the pr-reviewer agent to consume — not root-cause analysis. Streamlined three-phase flow that skips Phases 2–8; full procedure lives in rules/review-mode.md. |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +18 lines 9f84bc0320e9
- 7d ago First seen · 359 lines · 224 tokens per session scan A bee45d66e8d0
holistic-analysis is a skill published in the GitHub repository mthines/agent-skills (12 stars, last pushed yesterday), licensed MIT. It adds 224 tokens to every session and 4,274 once invoked, about $0.0011 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
debugging-and-error-recovery
Enforces a stop-the-line triage protocol across failure classes — test failures, build breaks, runtime errors, and production incidents — using bisection, safe-fallback design, and instrumentation lifecycle management. Use when any unexpected failure appears and the question is "what class of failure is this and…
debug
Runs a tight four-phase loop — reproduce, isolate, diagnose, fix — to root-cause a single bug with evidence, not guesses. Use when given a specific error message, stack trace, or unexpected behavior for one bug and need a fast, mechanical session (reproduce → isolate → diagnose → fix → prevention). For broader…
go-expert
Use when writing or reviewing Go code that starts goroutines, holds a sync.Mutex/RWMutex, or closes channels - to enforce goroutine lifecycle ownership, lock-hygiene, and channel-close-side rules, and to wire up the detection tooling (go test -race, go vet, go.uber.org/goleak) that catches violations tests alone…
layered-logging-and-alerting-patterns
Guides services where a single logging call fans out to multiple side effects - error tracking (e.g. Sentry), a centralized log-shipping endpoint, and chat/webhook alerting - rather than just writing a log line. Use when adding a log statement to a service with this shape, reviewing why removing a "log statement"…
security-analysis
Runs a two-pass vulnerability scan on a snippet, file, or diff — a static pattern pass across fixed categories (injection, secrets, auth, crypto, deserialization, path traversal, resource exhaustion), then an LLM-reasoning pass for business-logic and race-condition flaws the patterns can't catch. Use for a dedicated…
bug-triage-and-severity-classification
This skill should be used when the user asks to "triage this bug", "what severity is this", "classify this incident/bug", "is this a Sev1 or Sev2", "what priority should this ticket be", or is deciding SLA/response urgency for a reported defect. Use for assigning severity and priority to bugs and incidents…