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/johnrogers/claude-swift-engineering/reflectgit clone --depth 1 https://github.com/johnrogers/claude-swift-engineeringWrote 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/johnrogers/claude-swift-engineering/reflect)<a href="https://agentmods.dev/commands/johnrogers/claude-swift-engineering/reflect"><img src="https://agentmods.dev/badge/commands/johnrogers/claude-swift-engineering/reflect.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00459 |
| Opus 5 | $0.00000 | $0.00230 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
reflect 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 5d 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
You are an expert in prompt engineering, specializing in optimizing AI code assistant instructions. Your task is to analyze and improve the instructions for Claude Code. Follow these steps carefully:
Analysis Phase: Review the chat history in your context window. Then, examine the current Claude instructions, commands and config <claude_instructions> /CLAUDE.md /.claude/commands/* **/CLAUDE.md .claude/settings.json .claude/settings.local.json </claude_instructions>
Analyze the chat history, instructions, commands and config to identify areas that could be improved. Look for:
Inconsistencies in Claude's responses Misunderstandings of user requests Areas where Claude could provide more detailed or accurate information Opportunities to enhance Claude's ability to handle specific types of queries or tasks New commands or improvements to a commands name, function or response Permissions and MCPs we've approved locally that we should add to the config, especially if we've added new tools or require them for the command to work Interaction Phase: Present your findings and improvement ideas to the human. For each suggestion: a) Explain the current issue you've identified b) Propose a specific change or addition to the instructions c) Describe how this change would improve Claude's performance Wait for feedback from the human on each suggestion before proceeding. If the human approves a change, move it to the implementation phase. If not, refine your suggestion or move on to the next idea.
Implementation Phase: For each approved change: a) Clearly state the section of the instructions you're modifying b) Present the new or modified text for that section c) Explain how this change addresses the issue identified in the analysis phase
Output Format: Present your final output in the following structure:
[List the issues identified and potential improvements] [For each approved improvement: 1. Section being modified 2. New or modified instruction text 3. Explanation of how this addresses the identified issue] <final_instructions> [Present the complete, updated set of instructions for Claude, incorporating all approved changes] </final_instructions>
Remember, your goal is to enhance Claude's performance and consistency while maintaining the core functionality and purpose of the AI assistant. Be thorough in your analysis, clear in your explanations, and precise in your implementations.
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.
- 5d ago First seen · 24 lines · 0 tokens per session scan A 2e89d2fbd2c5
reflect is a command published in the GitHub repository johnrogers/claude-swift-engineering (228 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 459 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
prompt
System instructions for writing effective prompts. Apply when generating commands, skills, agents, or any LLM instructions.
prompt-show
Display full details of a saved prompt by ID.
music-suno-prompt
Grounded Suno prompt synthesis from local knowledge corpus + persona canon + label canon. No vibes-prompting.
prompt-optimize
Present the efficiency-versus-effectiveness frontier as labelled variants and let the user pick. TRIGGER WHEN: the user wants to review or optimize a prompt, system message, or agent instructions for clarity/tokens/reliability.
audit-prompt
Evaluate an existing prompt for clarity, effectiveness, and edge cases.
develop-image-prompt.eval
Generates a detailed image generation prompt from a document or content description. Good output: a prompt that is specific, visual, non-abstract, includes style/composition/lighting guidance, and is calibrated to the specified dimensions and style options.