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 petekp/claude-code-setup --skill exhaustive-systems-analysisgit clone --depth 1 https://github.com/petekp/claude-code-setupWrote 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/petekp/claude-code-setup/exhaustive-systems-analysis)<a href="https://agentmods.dev/skills/petekp/claude-code-setup/exhaustive-systems-analysis"><img src="https://agentmods.dev/badge/skills/petekp/claude-code-setup/exhaustive-systems-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.00102 | $0.01773 |
| Opus 5 | $0.00051 | $0.00886 |
| Sonnet 5 | $0.00020 | $0.00355 |
| Haiku 4.5 | $0.00010 | $0.00177 |
Grade A, and why
exhaustive-systems-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 6d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exhaustive Systems Analysis
Use this skill for full-system correctness work. The job is to map the system, identify the highest-risk behaviors, prove or refute concrete failure hypotheses, and leave behind a report another engineer can act on without re-reading the whole codebase.
Failure Modes To Prevent
- Surface-level audits that scan files without following behavior end-to-end
- False certainty: reporting suspicions as bugs without enough evidence
- Context drift across large audits with many subsystems
- Cosmetic reviews that miss the real correctness and ship-readiness risks
Operating Mode
- Default to
chat-firstoutput. Return findings inline unless the user asks for docs or the audit clearly needs multi-session artifacts. - Switch to
artifact modefor large or resumable audits. Usedocs/audit/or.claude/docs/audit/, matching the repo's existing conventions. - Do not start fixing code while auditing unless the user explicitly asks for fixes. This skill is for diagnosis, proof, and prioritization.
Workflow
0. Calibrate The Audit
Before reading deeply, write a one-screen scope brief using the template in references/templates.md.
Capture:
- system or area under review
- user-visible workflows or contracts that matter most
- likely high-risk surfaces: state, side effects, concurrency, auth, persistence, external integrations
- out-of-scope areas
- output mode:
chat-firstorartifact mode
If the request is broad, narrow it to the modules that can actually change user outcomes or ship readiness.
1. Load Intent Before Code
Read only the materials that establish intended behavior:
README,CLAUDE.md, architecture docs, ADRs- tests that describe user-visible or contract behavior
- recent commits touching the target area
TODO,FIXME,HACK, and "known issues"- incident notes, bug reports, or issue tracker items if available
Extract:
- critical workflows
- external surfaces
- hotspots and recent churn
- manual-only surfaces that cannot be fully verified from code alone
What ships with it
3 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.
- 6d ago First seen · 187 lines · 102 tokens per session scan A 56954132fb8a
exhaustive-systems-analysis is a skill published in the GitHub repository petekp/claude-code-setup (47 stars, last pushed 2d ago), licensed MIT. It adds 102 tokens to every session and 1,773 once invoked, about $0.0005 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
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
node-inspect-debugger
Debug Node.js via --inspect + Chrome DevTools Protocol CLI.
agent-introspection-debugging
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.
inspecting-hermes-desktop-dom
Read the live Hermes desktop DOM/CSS over CDP.
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.