agentmods.dev

using-powerups

using-powerups is a command for Claude Code from yeaight7/agent-powerups. It costs 0 tokens per session (345 once invoked), scanned A, original, Apache-2.0.

A command guide for finding and using installed Agent Powerups, which are reusable tools and instructions for coding agents.

In plain words
What is it for?
It helps discover, inspect, inventory, and select the most suitable installed asset for a coding task.
Why use it?
It avoids guessing which add-on is available or using one without checking its requirements.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code; mentions AGENTS.md; mentions Codex.

Part of the dev-vitals plugin — 14 skills, 4 commands, 1 agent shipped together

not rated 6repo 2d ago A scan 0 tokens original Apache-2.0

Good fit It helps discover, inspect, inventory, and select the most suitable installed asset for a coding task.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/yeaight7/agent-powerups/using-powerups
View source ↗ yeaight7/agent-powerups
Install

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.

Clone the repo
git clone --depth 1 https://github.com/yeaight7/agent-powerups

Made for: Claude Code.

Or install dev-vitals, the plugin that ships this one along with the rest of its 14 skills, 4 commands, 1 agent.

Wrote 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.

agentmods badge for using-powerups

README.md
[![agentmods](https://agentmods.dev/badge/commands/yeaight7/agent-powerups/using-powerups/github.svg)](https://agentmods.dev/commands/yeaight7/agent-powerups/using-powerups)
Your own site
<a href="https://agentmods.dev/commands/yeaight7/agent-powerups/using-powerups"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/using-powerups/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.

agentmods 80×15 button for using-powerups

Your own site · 80×15
<a href="https://agentmods.dev/commands/yeaight7/agent-powerups/using-powerups"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/using-powerups.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 345 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00345
Opus 5 $0.00000 $0.00172
Sonnet 5 $0.00000 $0.00069
Haiku 4.5 $0.00000 $0.00034

Measured yesterday against content hash 7b25300cc8a9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-15, from the pricing page.

Security

Grade A, and why

using-powerups 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.

plugins/dev-vitals/commands/using-powerups.md · 27 lines

What it actually says

using-powerups

Purpose: Find and apply installed Agent Powerups without guessing.

Use this prompt when starting non-trivial work in a repo where Agent Powerups may be installed.

Steps:

  1. Discover or match available assets:
    • Claude Code: start with native skill discovery when skills are already exposed by the host.
    • Codex, Gemini, and generic agents: start with apx discover.
    • Use apx discover when uncertain or when the task may need non-skill assets.
    • Use apx inventory for MCP configs, hooks, AGENTS.md templates, plugin-contained assets, staged assets, and installed-only assets.
    • apx discover "<user task>" --target <codex|claude-code|gemini|generic>
    • apx inventory --target <codex|claude-code|gemini|generic> --json
    • apx list --json --verbose
  2. Pick the narrowest asset that matches the user task.
  3. Inspect it before using:
    • apx info <asset-name>
    • read the asset file when needed
  4. Run apx check <asset-name> only when the asset declares external requirements or its instructions require a dependency check.
  5. If a dependency is missing, stop that path and report the exact missing tool. Ask before installing anything.
  6. Apply the asset only within the user-requested scope.
  7. Report which powerup was used, whether a dependency check was needed, validation run, and any fallback.

Do not enable MCP servers, install packages, mutate shell profiles, activate hooks, or write secrets unless the user explicitly asks.

Changes

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.

  1. yesterday First seen · 27 lines · 0 tokens per session scan A 7b25300cc8a9

Subscribe to this mod's changes

using-powerups 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 345 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.

Building agentsagentagent-skillagent-skillsagentsgemini-cli-extensionplugin
Related

Other commands, from other repositories

speckit.superspec.brainstorm

../../.specify/extensions/superspec/.specify-dev/agent-commands/kilocode/speckit.superspec.brainstorm.md.

HelixDevelopment/code · 0 tokens

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.

perniemann/pnCore · 38 tokens

gan-design

Run a generator/evaluator design loop for frontend or visual work with bounded iterations and scoring.

DekaPrayoga/AurixAgent · 18 tokens

orchestrate

Legacy slash-entry shim for dmux-workflows and autonomous-agent-harness. Prefer the skills directly.

DekaPrayoga/AurixAgent · 20 tokens

model-route

Recommend the best model tier for the current task based on complexity, risk, and budget.

DekaPrayoga/AurixAgent · 18 tokens

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens