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 john-wilmes/claude-agentic-coding-playbook --skill investigategit clone --depth 1 https://github.com/john-wilmes/claude-agentic-coding-playbookWrote 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/john-wilmes/claude-agentic-coding-playbook/investigate)<a href="https://agentmods.dev/skills/john-wilmes/claude-agentic-coding-playbook/investigate"><img src="https://agentmods.dev/badge/skills/john-wilmes/claude-agentic-coding-playbook/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/john-wilmes/claude-agentic-coding-playbook/investigate"><img src="https://agentmods.dev/badge/skills/john-wilmes/claude-agentic-coding-playbook/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.00082 | $0.06518 |
| Opus 5 | $0.00041 | $0.03259 |
| Sonnet 5 | $0.00016 | $0.01304 |
| Haiku 4.5 | $0.00008 | $0.00652 |
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 9d 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 — 712 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Investigate (v2)
Manage structured investigations.
Install Root Discovery
Before any subcommand, determine where the playbook's .claude/ directory is installed. The install root may differ from ~/.claude/ if the user ran install.sh --root <path>.
Run the install-root discovery helper:
INSTALL_ROOT=$(bash ~/.claude/scripts/skills/find-install-root.sh)
Set INVESTIGATIONS_DIR to <INSTALL_ROOT>/.claude/investigations.
Set TEMPLATES_DIR to <INSTALL_ROOT>/.claude/templates/investigation.
Argument Parsing
Parse $ARGUMENTS into:
- id: The investigation identifier (e.g.,
AUTH-001,SLOW-QUERY). Required for all subcommands exceptlistandsearch. - subcommand: One of
new,run,collect,synthesize,close,status. If omitted, auto-detect from STATUS.md.
Special forms:
/investigate list-- no id needed/investigate search <query>-- query is everything after "search"/investigate <id>-- auto-detect phase/investigate <id> <subcommand>-- explicit phase
Subcommand: list
List all investigations with their status and tags.
Steps
- Glob for
$INVESTIGATIONS_DIR/*/STATUS.md(exclude_patterns/). - For each investigation, read STATUS.md to get current phase and FINDINGS.md frontmatter for tags.
- Present as a table:
| ID | Phase | Domain | Type | Updated |
|----|-------|--------|------|---------|
If no investigations exist, say so and suggest /investigate <id> new.
Subcommand: search
Search investigations by text content or tag values.
Steps
- Parse the query from
$ARGUMENTS(everything after "search"). - Check if query matches a tag pattern (e.g.,
domain:ehr,type:root-cause). If so, search FINDINGS.md YAML frontmatter for matching values. - Otherwise, grep across all investigation files for the query text.
- Present matching investigations with context snippets.
Subcommand: new
Create a new investigation scaffold.
What ships with it
2 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.
- 9d ago First seen · 712 lines · 0 tokens per session scan A af3cda3a03db
investigate is a skill published in the GitHub repository john-wilmes/claude-agentic-coding-playbook (4 stars, last pushed 5mo ago), licensed MIT. It adds 82 tokens to every session and 6,518 once invoked, about $0.0004 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
rust-skills
Comprehensive Rust coding guidelines with 265 rules across 26 categories. Use when writing, reviewing, or refactoring Rust code. Covers ownership, error handling, async patterns, concurrency, unsafe code, API design, memory optimization, performance, numeric safety, conversions, serde, pattern matching, macros…
harness-init
Bootstrap target-repo root-truth files (AGENTS, CLAUDE, steering) in five phases with one user confirmation. Agent-native; no Node/npm required.
pipeline-quality-audit
Audit and improve media or AI-generation pipelines whose command may succeed while the delivered output is unusable. Use direct output evidence, attempt automatic repair/retry/fallback, quarantine bad attempts for diagnosis, and stop only when no valid deliverable can be produced.
project-ai-docs-steward
Audit AI entry docs (AGENTS, CLAUDE, steering, skills). Report first; edit only after approval. Use after init or when context drifts.
doc-governance
Audit and converge a repository's human documentation using the governance model proven in practice: single source of truth, lifecycle-tiered docs (current truth / lessons / validation), project content kept out of pipeline docs, dead docs deleted instead of archived, and honest evidence labels. Use when docs feel…
review
Review all uncommitted changes against project standards before committing.