Borrowing it
Nothing to install: this file belongs to grandinh/mcp-prompt-optimizer. 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/grandinh/mcp-prompt-optimizer/main/.claude/commands/README.mdgit clone --depth 1 https://github.com/grandinh/mcp-prompt-optimizerWrote 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/grandinh/mcp-prompt-optimizer/readme)<a href="https://agentmods.dev/commands/grandinh/mcp-prompt-optimizer/readme"><img src="https://agentmods.dev/badge/commands/grandinh/mcp-prompt-optimizer/readme/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/grandinh/mcp-prompt-optimizer/readme"><img src="https://agentmods.dev/badge/commands/grandinh/mcp-prompt-optimizer/readme.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.00462 |
| Opus 5 | $0.00000 | $0.00231 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
README 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.
What it actually says
Custom Slash Commands
This directory contains custom Claude Code slash commands for the MCP Prompt Optimizer project.
Available Commands
/ori - Optimize Research Implement
Purpose: Autonomous workflow for researching, validating, and implementing changes with minimal user input.
Usage:
/ori <your request>
Examples:
# Add a new feature
/ori add JWT authentication to the Express API
# Fix a bug
/ori fix the memory leak in the data processing pipeline
# Optimize performance
/ori optimize database queries for the user dashboard
# Research and implement best practices
/ori add rate limiting to all API endpoints using industry standards
What it does:
- Phase 1: Research - Automatically searches web, docs, and codebase
- Phase 2: Verify - Cross-validates findings and checks for risks
- Phase 3: Implement - Applies changes with error handling
- Phase 4: Document - Updates README, CHANGELOG, and other docs
Configuration:
Edit .claude/ori-config.json to customize behavior:
- Auto-approve low-risk changes
- Research depth and source count
- Documentation update preferences
- Error handling settings
Full Documentation: See ori.md
Creating Custom Commands
To create a new slash command:
- Create a new
.mdfile in this directory:.claude/commands/your-command.md - Write the command specification/prompt
- Use the command:
/your-command <args>
Example:
# Create .claude/commands/test.md with content:
# "Run all tests in the project and report results"
# Then use it:
/test
Command Best Practices
- Be specific - Clear commands get better results
- Provide context - Include tech stack, constraints when relevant
- Review output - Check implementation before committing
- Use config - Customize behavior via config files
- Iterate - Refine commands based on results
Last updated: 2025-11-08
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 · 78 lines · 0 tokens per session scan A cd116c12c86d
README is a command published in the GitHub repository grandinh/mcp-prompt-optimizer (0 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 462 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.