Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/d-mariano/spicyclaude/claude)<a href="https://agentmods.dev/commands/d-mariano/spicyclaude/claude"><img src="https://agentmods.dev/badge/commands/d-mariano/spicyclaude/claude/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/d-mariano/spicyclaude/claude"><img src="https://agentmods.dev/badge/commands/d-mariano/spicyclaude/claude.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.00960 |
| Opus 5 | $0.00000 | $0.00480 |
| Sonnet 5 | $0.00000 | $0.00192 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
CLAUDE 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Slash Commands
Overview
This directory contains custom slash command definitions for Claude Code. Slash commands are user-defined operations that expand to full prompts, enabling consistent workflows and specialized task execution.
Architecture
Command Configuration Format
Commands are defined using markdown files with YAML frontmatter:
allowed-tools: List of tools the command can use (supports wildcards likeBash(git add:*))argument-hint: Optional parameter hints shown to users (e.g.,[topic],[prd] [research])description: Brief explanation of the command's purpose
Command Body
The markdown body contains the prompt template with parameter placeholders:
$1,$2, etc. reference command arguments- Commands can include instructions, constraints, and output formatting
- Can specify file paths for output (e.g.,
/context/{feature|branch}/plan.md)
Available Commands
Development Workflow
- research (
research.md): Explore codebase and conduct web searches to understand a topic or PRD without writing code - plan (
plan.md): Create detailed implementation plan based on PRD and research - execute (
execute.md): Write elegant code implementing the plan, respecting CLAUDE.md principles - explore (
explore.md): Alternative research command for gaining context
Code Quality
- pragmatic-code-review (
pragmatic-code-review.md): Conduct pragmatic code review on current branch - design-review (
design-review.md): Comprehensive UI/UX design review with automated testing - simplify (
simplify.md): Refactor and simplify code
Utilities
- crawl (
crawl.md): Generate/update CLAUDE.md documentation files - pr (
pr.md): Create pull request workflow - next (
next.md): Determine next steps - quick (
quick.md): Quick task execution
Custom Development Workflows
- my-developer-plan (
my-developer-plan.md): Custom planning workflow - my-developer-review (
my-developer-review.md): Custom review workflow
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.
- 9d ago First seen · 93 lines · 0 tokens per session scan A c329c964b677
CLAUDE is a command published in the GitHub repository d-mariano/spicyclaude (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 960 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-31.
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.