Borrowing it
Nothing to install: this file belongs to jmanhype/speckit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jmanhype/speckit/main/.claude/commands/_example-command.mdgit clone --depth 1 https://github.com/jmanhype/speckitWrote 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/jmanhype/speckit/_example-command)<a href="https://agentmods.dev/commands/jmanhype/speckit/_example-command"><img src="https://agentmods.dev/badge/commands/jmanhype/speckit/_example-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/jmanhype/speckit/_example-command"><img src="https://agentmods.dev/badge/commands/jmanhype/speckit/_example-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.00364 |
| Opus 5.5 | $0.00000 | $0.00146 |
| Sonnet 5.5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
_example-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
Example Custom Slash Command
This is a template for creating your own custom slash commands. Rename this file to your-command-name.md and customize it. Delete this file if you don't need it.
Usage
/project:example-command <your arguments here>
What This Command Does
This command template demonstrates the key features of custom slash commands:
- $ARGUMENTS - Captures everything after the command name
- Structured prompts - Guide Claude through specific steps
- Tool suggestions - Recommend specific tools for tasks
Command Prompt
Analyze and work on: $ARGUMENTS
Follow these steps:
-
Understand the Request
- Parse what the user is asking for
- Identify key requirements and constraints
-
Research the Codebase
- Use
Globto find relevant files - Use
Grepto search for patterns - Use
Readto examine file contents
- Use
-
Plan the Approach
- Outline the steps needed
- Identify potential challenges
- Consider edge cases
-
Implement Changes
- Make targeted edits using
Edit - Create new files only if necessary using
Write - Run tests to verify changes
- Make targeted edits using
-
Verify and Clean Up
- Run linting and type checking
- Ensure tests pass
- Create a descriptive commit message
Notes
- Commands in
.claude/commands/are project-specific - Commands in
~/.claude/commands/are available globally - Use descriptive filenames:
fix-github-issue.md,deploy-staging.md - The
$ARGUMENTSkeyword passes user input to the prompt
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 · 57 lines · 0 tokens per session scan A 6a2e6d4591ea
_example-command is a command published in the GitHub repository jmanhype/speckit (26 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 364 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-09-01.
Other commands, from other repositories
paul:help
Show available PAUL commands and usage guide.
lavra-work-teams
Work on multiple beads with persistent worker teammates that self-organize through a ready queue.
lavra-work-ralph
Autonomous retry mode for bead work -- iterates until completion criteria are met or retry budget is exhausted.
lavra-import
Import a markdown plan into beads as an epic with child tasks.
paul:verify
Guide manual user acceptance testing of recently built features.
clarify
Reduce spec ambiguity via targeted questions with adaptive auto-invocation (planning is 80% of success).