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 jameslowman/planning-with-james --skill diggit clone --depth 1 https://github.com/jameslowman/planning-with-jamesWrote 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/jameslowman/planning-with-james/dig)<a href="https://agentmods.dev/skills/jameslowman/planning-with-james/dig"><img src="https://agentmods.dev/badge/skills/jameslowman/planning-with-james/dig.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.00000 | $0.02789 |
| Opus 5 | $0.00000 | $0.01394 |
| Sonnet 5 | $0.00000 | $0.00558 |
| Haiku 4.5 | $0.00000 | $0.00279 |
Grade C, and why
dig scanned grade C with 1 finding 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
If the knowledge graph is behind HEAD (detected in Step 1), prefix findings with a caveat and suggest running `/planning-with-james:update-knowledge` after exploring. Do not refuse to answer -- stale knowledge is still b How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Query the Knowledge Graph
NON-NEGOTIABLE: ALL PATHS ARE RELATIVE TO THE REPO ROOT
All .claude/planning-with-james/ paths in this skill are relative to the current working directory (the repo you're working in), NOT ~/.claude/. The knowledge graph lives inside the project, not in your home directory. If you're unsure, run pwd to confirm you're in the repo root.
NON-NEGOTIABLE: THIS SKILL ONLY READS THE KNOWLEDGE GRAPH, NEVER UPDATES IT
If the knowledge graph is missing or stale, inform the user and suggest they run /planning-with-james:create-knowledge or /planning-with-james:update-knowledge. Do NOT run those skills yourself. Do NOT modify any knowledge files.
NON-NEGOTIABLE: KNOWLEDGE GRAPH IS YOUR PRIMARY SOURCE This skill exists because the knowledge graph already contains deep analysis of module boundaries, key files, public interfaces, internal patterns, cross-module dependencies, and documented gotchas. You MUST answer from the knowledge graph first. Only fall back to source code when the knowledge graph has an explicit gap.
This is a stateless, lightweight skill. No phases, no state files, no registry entries. Answer the user's question and offer to save findings. That's it.
Step 1: Verify Knowledge Graph Exists
Read .claude/planning-with-james/knowledge/_overview.md.
- If missing: Tell the user there is no knowledge graph for this repo. Suggest running
/planning-with-james:create-knowledgefirst. Stop here. - If present: Check the
last_commitin the frontmatter. Compare it to the current HEAD (git rev-parse HEAD). If they differ, note this as a caveat: "The knowledge graph was last updated at commit {hash}. There have been changes since. Findings may not reflect recent code." Continue.
Step 2: Handle Empty Arguments
If $ARGUMENTS is empty or blank, ask the user what they want to explore using AskUserQuestion:
Question: "What do you want to explore? You can ask about how something works, what would be affected by a change, trace a flow through the system, or review your current diff."
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 · 223 lines · 0 tokens per session scan C 0a034b548f3c
dig is a skill published in the GitHub repository jameslowman/planning-with-james (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,789 tokens. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…