Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ihudak/ihudak-claude-plugins/plugin install workflows-coreWrote 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/ihudak/ihudak-claude-plugins/prompt)<a href="https://agentmods.dev/commands/ihudak/ihudak-claude-plugins/prompt"><img src="https://agentmods.dev/badge/commands/ihudak/ihudak-claude-plugins/prompt/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/ihudak/ihudak-claude-plugins/prompt"><img src="https://agentmods.dev/badge/commands/ihudak/ihudak-claude-plugins/prompt.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.00050 | $0.01443 |
| Opus 5.5 | $0.00020 | $0.00577 |
| Sonnet 5.5 | $0.00010 | $0.00289 |
| Haiku 4.5 | $0.00005 | $0.00144 |
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 23d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Log a corrective interaction and act on it: $ARGUMENTS
/prompt is for when a command of this plugin family (/specify, /design,
/implement, /document, …) produced something wrong and you want to correct
it directly. It captures the corrective triple as plugin feedback, then
performs the correction. origin: prompt.
Captured (per ${CLAUDE_PLUGIN_ROOT}/references/feedback-emission.md §1):
- Friction — what the command produced that was wrong.
- User prompt — your corrective request, verbatim (
$ARGUMENTS). - Resolution — what the AI actually did.
Phase 0 — Specs-repo preflight
Cite ${CLAUDE_PLUGIN_ROOT}/references/specs-repo-git.md and execute its
specs-preflight entry point (§3) inline: flush any leftover session
artifacts from an earlier run, retry an artifact commit that failed to push,
and settle the branch. This runs against $SPECS_PATH only — git -C "$SPECS_PATH", never a cd, so whatever repository you are standing in is
untouched (§1 rule 1). Prompt-free and silent when the specs repo is clean and
on its default branch. If a guard fires, emit its §5 notice; if it returns
specs_git: blocked (§3.3 G0), carry that flag — the terminal
commit-artifacts step skips on it.
Phase 1 — Identify the target
Infer the target command from recent context — which command's output you are
correcting. Ask only if genuinely ambiguous (one grouped prompt of 2–4 options; the
harness supplies the free-text escape). If no command applies, use n/a. Normalise the answer
before it travels: target_command must be a bare ${CLAUDE_PLUGIN_ROOT}/references/cost-emission.md
§7 row name (/document, never /document (keyed mode)), so map a free-text
answer onto the row it names and use n/a when it names none — an unnormalised
value matches no row and silently degrades the entry to plugin-feedback/n/a.
Phase 2 — Act on the correction
Perform the corrective request in $ARGUMENTS directly (the quick correction).
Keep a one-line summary of what you did — this becomes the Resolution block.
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.
- 23d ago Changed 56a1cd95c639
- 28d ago Changed e49f4bb3929c
- 1mo ago First seen · 103 lines · 50 tokens per session scan A 428dd7c40191
prompt is a command published in the GitHub repository ihudak/ihudak-claude-plugins (2 stars, last pushed 24d ago), licensed MIT. It adds 50 tokens to every session and 1,443 once invoked, about $0.0002 per session on Opus 5.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-05.
Other commands, from other repositories
battlecard
Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and win strategies.
cloudflare-r2:presigned-url
Generate presigned URLs for secure client-side uploads or downloads.
commit
Context-aware Git commit assistant with smart pre-commit checks.
infogenius
Research-First Image Generation - Facts → Visual Prompt → High-Quality Image.
pi-code-review
Adversarial code review via Codex — break confidence in changes, not validate them.
watch
You are executing the /hydra:watch command. Live monitoring of all background agents with real-time status updates.