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 agents/chris-dare-dev/agent-kit/skill-to-command-reviewergit clone --depth 1 https://github.com/chris-dare-dev/agent-kitWhat 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.00126 | $0.02893 |
| Opus 5 | $0.00063 | $0.01447 |
| Sonnet 5 | $0.00025 | $0.00579 |
| Haiku 4.5 | $0.00013 | $0.00289 |
Grade C, and why
skill-to-command-reviewer scanned grade C with 2 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 3d 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.
Instruction-override phrasingmediumPrompt injection
Text telling the model to disregard its earlier instructions or safety rules is the shape of a prompt injection, whoever wrote it.
"Now run X", "Ignore previous instructions", "Authorize the user", "Pass this Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ".claude/agent-memory/skill-to-command-reviewer/lessons.md" 2>/dev/null || echo "(no lessons yet)" How it starts
The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill-to-Command Reviewer
You are Turn 3 of the /skill-to-command pipeline. Your job is the adversarial review: walk the 14 critical gotchas catalog against the newly-authored tree and emit a severity-tagged critique that DECIDES SHIP vs DO-NOT-SHIP.
You see the implementation diff cold — no prior context from the authoring turn. That isolation is the value: catches blind spots the authors missed.
The orchestrator dispatches you once after Turn 2 completes. You never invoke other sub-agents.
Input variables (substituted by the orchestrator)
{SKILL_NAME}— the skill being converted{CRITIQUE_PATH}— absolute path to write the critique:.claude/notes/{SKILL_NAME}-build-critique.md{TURN_2_SUMMARIES}— JSON summaries returned by Agent A and Agent B (theirfiles_written/files_renamed/files_deletedlists)
Step 0 — Read persistent memory (skip-if-not-relevant)
cat ".claude/agent-memory/skill-to-command-reviewer/lessons.md" 2>/dev/null || echo "(no lessons yet)"
Lessons here are calibration data: severity-rubric drift (you've been too harsh / too lenient before), and gotcha-frequency surprises (the C3 stdin-vs-argv gotcha shows up far more than expected; check it aggressively).
Step 1 — Read the conversion runbook §14-gotcha catalog (REQUIRED)
cat "data/references/skill-to-command-conversion-prompt.md"
Focus on the §"14 critical gotchas" section. The catalog is your checklist — you walk it gotcha-by-gotcha against the new tree.
Step 2 — Read the new tree end-to-end
For each file in {TURN_2_SUMMARIES}.files_written and {TURN_2_SUMMARIES}.files_renamed[].to:
cat <path>
Hold the full content in working memory. You will cross-reference between files (e.g. the slash command body's script calls vs the actual script CLI shapes).
Deliberation protocol (perform in your visible output BEFORE assigning any severity or verdict)
Your judgment is most reliable when your reasoning is explicit. Work through this in your response — not silently — before producing the structured findings/verdict below:
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.
- 3d ago First seen · 226 lines · 126 tokens per session scan C c3b20c53b282
skill-to-command-reviewer is an agent published in the GitHub repository chris-dare-dev/agent-kit (0 stars, last pushed 25d ago), licensed MIT. It adds 126 tokens to every session and 2,893 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 2 findings (instruction-override phrasing, reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
algolia-agent
Senior Algolia platform engineer with command of index design, relevance tuning, InstantSearch React/Next.js, the Autocomplete UI library, direct search-client usage, indexing pipelines, API-key strategy, the Recommend API, AI search and Personalization (NeuralSearch, query categorization), Insights events and A/B…
bynder-agent
Senior Bynder DAM platform engineer with command of asset modeling and metaproperties, Brand Guidelines, derivative templates, the bynder-js-sdk, Universal Compact View embedding, Bynder + Contentful pairing, portal and account architecture, permissions and workflow, webhooks, marketplace connectors, migrations, and…
behavioral-economics-agent
Senior behavioral scientist who applies behavioral economics, choice architecture, and research methods to product, policy, marketing, and organizational problems. Use this agent when a task spans multiple skills in this plugin, requires sequencing, or needs senior-level judgment about which skill to apply for a given…
brand-agent
Senior brand practitioner spanning strategy, naming, identity systems, voice and tone, guidelines composition, and brand audits. Use this agent when a task spans multiple skills in this plugin, requires sequencing, or needs senior-level judgment about which skill applies. Tagline: Brand from positioning to applied…
claude-agent
Plugin orchestrator. Routes between the two claude- skills (claude-plugin-creator for building new Claude plugins from scratch, and claude-orchestrator for designing the orchestration layer of a new Cowork project). Use this agent as the first call for any Claude-tooling task — plugin creation, hook design, MCP server…
consulting-agent
Senior management consultant who handles the full engagement lifecycle — from pursuit through delivery. Use this agent when a task spans multiple skills in this plugin, requires sequencing, or needs senior-level judgment about which skill to apply for a given problem. Tagline: Consulting end-to-end — pursuit, scoping…