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/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/plan)<a href="https://agentmods.dev/commands/yeaight7/agent-powerups/plan"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/plan/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/yeaight7/agent-powerups/plan"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/plan.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.00140 |
| Opus 5 | $0.00000 | $0.00070 |
| Sonnet 5 | $0.00000 | $0.00028 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
plan 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.
What it actually says
plan
Use before starting any non-trivial task.
Steps:
- Re-read the user request in full. Identify the goal, constraints, and what "done" means.
- Map affected areas: run
git status --shortandapx listto see what exists. - List the files most likely to change. For each, read its current state with the Read tool.
- Write a numbered step list — small enough that each step is one logical change.
- Identify risks: external dependencies, breaking changes, missing context.
- Present the plan to the user and wait for approval before implementing.
Do not write code or modify files during planning.
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 · 15 lines · 0 tokens per session scan A c92cc3aad606
plan is a command published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 140 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-09-14.
Other commands, from other repositories
speckit.superspec.brainstorm
../../.specify/extensions/superspec/.specify-dev/agent-commands/kilocode/speckit.superspec.brainstorm.md.
pn-bolder
Amplify a timid, safe, or generic design — more visual weight, stronger personality, clearer point-of-view. Use when the design is technically correct but forgettable.
gan-design
Run a generator/evaluator design loop for frontend or visual work with bounded iterations and scoring.
orchestrate
Legacy slash-entry shim for dmux-workflows and autonomous-agent-harness. Prefer the skills directly.
model-route
Recommend the best model tier for the current task based on complexity, risk, and budget.
checklist
Generate a custom checklist for the current feature based on user requirements.