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/fusengine/agents/promptgit clone --depth 1 https://github.com/fusengine/agentsWrote 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/fusengine/agents/prompt)<a href="https://agentmods.dev/commands/fusengine/agents/prompt"><img src="https://agentmods.dev/badge/commands/fusengine/agents/prompt.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.00007 | $0.00789 |
| Opus 5 | $0.00003 | $0.00394 |
| Sonnet 5 | $0.00001 | $0.00158 |
| Haiku 4.5 | $0.00001 | $0.00079 |
Grade A, and why
prompt 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 yesterday.
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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/prompt Command
Command for creating or optimizing prompts using the prompt-engineer agent.
Usage
/prompt [action] [description]
Actions
| Action | Description |
|---|---|
create |
Create a new prompt |
optimize |
Improve an existing prompt |
agent |
Design a complete agent |
review |
Analyze an existing prompt |
Workflow
1. Action Detection
IF $ARGUMENTS contains "create" or "new":
→ Action: CREATE
IF $ARGUMENTS contains "optimize" or "improve":
→ Action: OPTIMIZE
IF $ARGUMENTS contains "agent" or "assistant":
→ Action: AGENT_DESIGN
IF $ARGUMENTS contains "review" or "analyze":
→ Action: REVIEW
ELSE:
→ Ask for clarification
2. Agent Launch
Launch prompt-engineer agent with:
- Appropriate skill loaded
- User context
- Identified constraints
3. Workflow Execution
For CREATE:
- Identify prompt type (system, task, few-shot, meta)
- Identify constraints (model, format, domain)
- Apply the 9-element Anthropic structure
- Generate prompt with appropriate techniques
- Validate with quality checklist
For OPTIMIZE:
- Analyze current prompt
- Identify issues (clarity, structure, completeness, guardrails)
- Apply corrections
- Generate before/after report
- Propose optimized prompt
For AGENT_DESIGN:
- Define identity and purpose
- Choose architecture pattern
- Define workflow
- Configure tools and skills
- Implement guardrails
- Generate complete agent.md file
For REVIEW:
- Analyze according to checklist
- Score each criterion (clarity, structure, completeness, guardrails)
- Identify strengths and weaknesses
- Propose recommendations
Examples
Create a system prompt
/prompt create a technical support assistant for a mobile app
Optimize an existing prompt
/prompt optimize [paste the prompt to improve]
Design an agent
/prompt agent a Python-specialized code reviewer
Analyze a 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.
- yesterday First seen · 173 lines · 7 tokens per session scan A e244fe1e6c3d
prompt is a command published in the GitHub repository fusengine/agents (25 stars, last pushed today), licensed MIT. It adds 7 tokens to every session and 789 once invoked, about $0.0000 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-03.
Other commands, from other repositories
fix-prompt
Fix and improve a rough prompt — show the cleaned version and the changes before acting on it.
test-prompt
Test an AI prompt against multiple scenarios to verify consistent, quality output.
token-cost-audit
Audit LLM call sites for token and cost waste, quantify the savings, and apply the safe wins.
prompt-optimize
Apply fixes for issues found by prompt-review.
boost
Pick how your prompt gets rewritten before you send it.
a
Intercept Mode - Auto-improve and execute immediately.