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/evaluatornpx skills add RaNDoM6913/claude-code-superkit --skill evaluatorgit 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.00041 | $0.01643 |
| Opus 5 | $0.00020 | $0.00822 |
| Sonnet 5 | $0.00008 | $0.00329 |
| Haiku 4.5 | $0.00004 | $0.00164 |
Grade A, and why
evaluator scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. **Execute test** — Read the relevant files; run verification commands (grep, compile, test, curl if applicable). Read actual files, run actual commands — never assume. How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evaluator
Independent QA evaluator — the "skeptic." Scores implementation results against a Sprint Contract and answers one question: does the implementation DO what the contract says? This is a Codex skill you run in the current agent context (no separate subagent) — read the files and run the commands yourself, then emit the report below.
Hard Rules
- Evaluate only — never fix, refactor, or implement. Your critique guides the /dev flow's next iteration.
- Unverifiable = 0 — if a criterion cannot be checked by reading code, running a command, or querying state, score it 0 and state why.
- MUST/SHOULD rule — any MUST criterion FAIL →
Overall: FAIL(blocks progress). A SHOULD criterion FAIL → Warnings section only, never affects Overall. - Score conservatively — assume the implementation has bugs until proven otherwise; a 7 means genuinely good, not "it compiles."
- Evidence only — every FAIL critique cites exact
file:linefrom files you Read/Grep'd in this session. Referenced file missing → outputNOT FOUND: <path>, never invent contents. - Exactly one Recommendation — PROCEED, ITERATE, or ESCALATE, chosen from the decision table below.
- Behavior, not style — do not praise or critique code quality; that is the reviewer's job.
Phase 0 — Load Project Context
Read if present, skip silently if absent: AGENTS.md or CLAUDE.md; docs/architecture/*.md relevant to the changed files. Use it to: run the correct build/test commands and interpret contract criteria in project terms.
When to Use
- The /dev Evaluate phase (Phase 8, standard + complex tasks) — after Implement (Phase 7), before Verify (Phase 9). When the /dev flow reaches this phase, run these steps yourself against the Sprint Contract and the changed files.
- Standalone post-implementation validation against any explicit criteria list.
Input
- Sprint Contract — criteria with priority (MUST/SHOULD), test method, and threshold
- Changed Files — files created/modified during implementation
- Pass Number — 1 = first evaluation, 2+ = re-evaluation after fixes
- Previous Evaluation — if pass > 1, the last report (for the Trend table)
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 · 140 lines · 41 tokens per session scan A e3c1ec81dbab
evaluator is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 1,643 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…