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 agentmods add skills/random6913/claude-code-superkit/plan-checkernpx skills add RaNDoM6913/claude-code-superkit --skill plan-checkergit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWhat 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 | $0.00024 | $0.00713 |
| Opus 5 | $0.00012 | $0.00357 |
| Sonnet 5 | $0.00005 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
plan-checker 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Checker
Validates implementation plans BEFORE execution begins. Catches incomplete, incorrect, or infeasible plans early — when fixing is cheap.
Phase 0: Load Project Context
Read if exists:
AGENTS.mdorCLAUDE.md— project conventions, file structure, tech stackdocs/architecture/— existing architecture (verify plan references match reality)
Use this context to:
- Verify file paths in plan actually exist (or parent dirs exist for new files)
- Check that plan follows project conventions
- Validate migration numbering against existing migrations
When to Use
- BEFORE Phase 3 (Implement) in
dev-orchestrator— mandatory gate - After writing any implementation plan
- Dispatched automatically by
dev-orchestrator
Validation Dimensions (8 checks)
1. Requirement Coverage (CRITICAL)
- Every stated goal has at least 1 task addressing it
- No requirements mentioned in description but missing from tasks
2. File Path Accuracy (CRITICAL)
- Every "Modify: path" → verify file exists
- Every "Create: path" → verify parent directory exists
- Flag wrong paths before execution wastes time
3. Dependency Order (HIGH)
- Migrations before code that uses new tables
- Interfaces before implementations
- API changes before consumers
4. Scope Sanity (HIGH)
- More than 15 tasks → suggest splitting
- More than 20 files → suggest phasing
- Tasks too vague ("update frontend") → request specifics
5. Convention Compliance (MEDIUM)
- Migration naming matches project pattern
- Files in correct layer directories
- Commit messages follow conventional format
6. Documentation Completeness (MEDIUM)
- API changed → doc update task exists?
- Migration added →
AGENTS.md/project docs counter update? - File structure changed → tree update?
7. Test Coverage (MEDIUM)
- New endpoints → test tasks?
- Business logic → service tests?
- Bug fixes → regression tests?
8. Factual Accuracy (CRITICAL)
- Claims about existing code → verify by reading actual files
- "Currently X does Y" → grep to confirm
- Number claims (endpoint count, migration count) → verify
- Most important check — catches assumptions that become bugs
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 First seen · 98 lines · 24 tokens per session scan A 650e5698fddd
plan-checker is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 713 once invoked, about $0.0001 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
apm-review-panel
Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. The panel fans out to five mandatory specialists plus a test-coverage specialist (active on every PR that touches src/) plus three conditional specialists (auth, doc-writer, performance-expert), all running in…
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
apm-spec-guardian
Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/.schema.json), or the conformance fixture seed…
apm-triage-panel
Use this skill to triage one microsoft/apm issue selected by the daily sweep, the status/needs-triage fast path, or manual dispatch. Emit one synthesized comment with a decision, label set, exact milestone, and suggested next action.
batch-bug-shepherd
Use this skill to drive a batch of suspected bugs in microsoft/apm from raw issue list to mergeable PR queue. Fan out one triage subagent per issue (LEGIT / UNCLEAR / FIXED-AT-HEAD), gate every legit bug against PRINCIPLES.md via an apm-ceo strategic-alignment pass, cross-reference legit issues against open PRs, then…
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…