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.
git clone --depth 1 https://github.com/shdennlin/agent-pluginsWrote 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/shdennlin/agent-plugins/build)<a href="https://agentmods.dev/commands/shdennlin/agent-plugins/build"><img src="https://agentmods.dev/badge/commands/shdennlin/agent-plugins/build/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/shdennlin/agent-plugins/build"><img src="https://agentmods.dev/badge/commands/shdennlin/agent-plugins/build.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.00027 | $0.00417 |
| Opus 5.5 | $0.00011 | $0.00167 |
| Sonnet 5.5 | $0.00005 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
build 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 12d 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
Build Command
Arguments
Parse $ARGUMENTS:
--helpor-h— Show usage information and exit--goal— Target/goal: keep the prompt under its 4000-character cap- Everything else — the input: a topic, a messy multi-task request, or an existing draft prompt to strengthen
Help Output
If --help or -h is present, display this and stop:
Usage: /prompt-builder:build [topic | draft prompt] [--goal]
Build a polished, self-contained prompt from messy input. Three modes, auto-detected:
context extract — mid-session with history: mine the conversation for the components
interview — cold start with a topic: ask only the questions that matter
critique — input is an existing prompt draft: diagnose and strengthen it
The finished prompt is printed as one copyable block and placed on the clipboard,
ready to paste after a rewind.
--goal shape it as a /goal condition and keep it under 4000 chars;
overflow spills to ~/.claude/prompt-builder/<slug>.md
Examples:
/prompt-builder:build fix the flaky auth test and write a migration note
/prompt-builder:build --goal (a /goal condition from this conversation)
/prompt-builder:build (uses the current conversation as source material)
/prompt-builder:build <paste an existing prompt draft to critique>
Instructions
If help was requested, stop here. Otherwise, invoke the prompt-builder skill with
$ARGUMENTS as the input (empty input is fine — the skill will draw on the
conversation or ask) and follow it exactly.
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.
- 12d ago Changed · +5 lines b985fc904ece
- 1mo ago First seen · 41 lines · 27 tokens per session scan A 9d6b4be68e61
build is a command published in the GitHub repository shdennlin/agent-plugins (2 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 417 once invoked, about $0.0001 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-11.
Other commands, from other repositories
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).
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.
ai
Load the Kaizen skill for production-ready AI agent implementation with signature-based programming and multi-agent coordination.
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.