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.
git clone --depth 1 https://github.com/LukeRenton/explore-claude-codeWrote 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/commands/lukerenton/explore-claude-code/my-command)<a href="https://agentmods.dev/commands/lukerenton/explore-claude-code/my-command"><img src="https://agentmods.dev/badge/commands/lukerenton/explore-claude-code/my-command/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/commands/lukerenton/explore-claude-code/my-command"><img src="https://agentmods.dev/badge/commands/lukerenton/explore-claude-code/my-command.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.00000 | $0.00368 |
| Opus 5.5 | $0.00000 | $0.00147 |
| Sonnet 5.5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
my-command 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 1mo 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.
What it actually says
Review the changes in this PR. Focus on:
- Correctness: Does the logic do what it claims?
- Security: Any injection risks, leaked secrets, or auth bypasses?
- Tests: Are edge cases covered?
- Style: Does it follow our conventions in CLAUDE.md?
For each issue found, classify as:
- Must fix: Bugs, security issues
- Should fix: Missing tests, unclear naming
- Nit: Style preferences, optional improvements
Start by running git diff main...HEAD to see all changes.
$ARGUMENTS
This is a starter command file. The filename my-command.md becomes the slash command /my-command.
Everything above the --- is the prompt that Claude receives when you invoke the command. $ARGUMENTS is replaced with whatever you type after the command name.
For example, /my-command focus on auth would replace $ARGUMENTS with "focus on auth".
What Makes a Good Command
- A clear, specific task (not open-ended)
- Context about your project's standards or conventions
- Structured output format so results are consistent
$ARGUMENTSto allow per-invocation customisation
Limitations
Commands are simple prompt templates. They do not support:
- Frontmatter (model overrides, invocation control, tool restrictions)
- Supporting files (scripts, references, assets)
- Dynamic context injection (
!backtick syntax) - Auto-loading based on task relevance
For any of those features, use a [skill](^Skills are the newer, more powerful replacement for commands. See the skills/ directory for the full structure) instead. Commands and skills create the same /slash-command interface.
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.
- 1mo ago First seen · 41 lines · 0 tokens per session scan A 2e450b9cb89a
my-command is a command published in the GitHub repository LukeRenton/explore-claude-code (319 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 368 tokens. 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-30.
Other commands, from other repositories
genshijin-review
A compact Japanese-language code-review command that reports one finding per line with a severity label and suggested fix.
review-open-prs
Command "review-open-prs" from The-Artificer-of-Ciphers-LLC/skills-from-the-artificer, covering batch pr review directive — all open prs i did not author, phase a — enumerate target prs & build the queue, phase b — per-pr directive (runs once per queued $pr), 0. context anchoring and 1. preconditions.
review
Recent git commits: !git log --oneline -10.
resolve-review
Resolve reviewer feedback - from GitHub PRs, chat, or any reviewer.
setup
Set up, configure, or reconfigure notabene and start the docs review server.
review
/review [optional: specific files or PR number].