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 commands/jnarowski/agentcmd/generate-slash-commandgit clone --depth 1 https://github.com/jnarowski/agentcmdWhat 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.00011 | $0.01341 |
| Opus 5 | $0.00005 | $0.00671 |
| Sonnet 5 | $0.00002 | $0.00268 |
| Haiku 4.5 | $0.00001 | $0.00134 |
Grade A, and why
generate-slash-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 today.
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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Slash Command
Create a new slash command following team conventions and best practices. Read Instructions and follow Workflow steps in exact order.
Variables
- $command-name: $1 (required) - The name of the command (e.g., "test", "commit", "generate-spec")
- $description: $2 (optional) - Brief description of what the command does
Instructions
- Normalize $command-name (lowercase, hyphenated) for the filename
- If command name is not provided, stop IMMEDIATELY and ask the user to provide one
- If description is not provided, stop IMMEDIATELY and ask the user to provide one
- All slash commands are markdown files in
.claude/commands/directory - Commands should be clear, actionable, and follow existing patterns
- Use frontmatter for metadata (description, argument-hint)
Workflow
-
Ask clarifying questions if needed: a. Ask questions ONE AT A TIME. b. Follow this template below (provide two options and specify which you recommend and why)
```md **Question**: The question you have **Suggestions** 1: Something (recommended) 2: Something else 3: Other - user specifies ```c. question examples
- Does this command take arguments?
- Does it generate a file or perform an action?
- Does it need to interact with external tools (git, npm, etc.)?
- Should it follow a specific template or workflow?
-
Once you have all context, generate the command file following the exact structure in Template below
-
Write the command to
.claude/commands/${command-name}.md -
Report the file path created
Slash Command Types
Action Commands
Commands that perform operations (commit, test, review)
- Focus on step-by-step instructions
- Include validation steps
- Provide clear success criteria
Generator Commands
Commands that create files from templates (generate-prd, generate-feature)
- Define variables and argument handling
- Include a complete template section
- Specify output file path
- Include formatting rules
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.
- today First seen · 209 lines · 11 tokens per session scan A 035d59d48a30
generate-slash-command is a command published in the GitHub repository jnarowski/agentcmd (18 stars, last pushed 8mo ago), licensed MIT. It adds 11 tokens to every session and 1,341 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-09-01.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.