using-powerups

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

A repository-startup guide for finding and applying reusable local instructions, commands, workflows, hooks, templates, or tool connections called Agent Powerups.

In plain words
What is it for?
It helps route tasks such as debugging, planning, code review, setup, file intake, cleanup, pull-request triage, tool configuration, and agent-instruction templates.
Why use it?
It prevents an agent from improvising when the repository already contains a suitable way to handle the task. It also says when no matching powerup should be used.

Skill 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

Good fit It helps route tasks such as debugging, planning, code review, setup, file intake, cleanup, pull-request triage, tool configuration, and agent-instruction templates.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yeaight7/agent-powerups/using-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.

Any agent
npx skills add yeaight7/agent-powerups --skill using-powerups
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/skills/yeaight7/agent-powerups/using-powerups/github.svg)](https://agentmods.dev/skills/yeaight7/agent-powerups/using-powerups)
Your own site
<a href="https://agentmods.dev/skills/yeaight7/agent-powerups/using-powerups"><img src="https://agentmods.dev/badge/skills/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/skills/yeaight7/agent-powerups/using-powerups"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/using-powerups.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,145 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.00043 $0.01145
Opus 5 $0.00022 $0.00573
Sonnet 5 $0.00009 $0.00229
Haiku 4.5 $0.00004 $0.00114

Measured yesterday against content hash e2ec2900e994, 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/skills/using-powerups/SKILL.md · 127 lines

How it starts

The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Using Powerups

Purpose

Find and apply installed Agent Powerups before improvising. A powerup is useful only after you discover likely matches, inspect the actual asset, follow its instructions, and verify the user task with task-specific evidence.

When to Use

Use at the start of non-trivial work, and again when the task changes shape.

Use when the user asks for debugging, planning, review, setup, file intake, cleanup, PR triage, second opinions, MCP config, hooks, commands, or AGENTS.md templates.

Do not force a powerup when none fits. Say no matching powerup applies and proceed normally.

Inputs

  • User task.
  • Current repo or agent root.
  • Installed agent-powerups location, usually agent-powerups/ under the agent root or the package repo.
  • Optional CLI access to apx for discovery and inventory.
  • Optional installed discovery index file; treat it as a derived snapshot, not the source of truth.

Workflow

  1. Discover or match available assets.

Use target-specific routing:

  • Claude Code: start with native skill discovery when skills are already exposed by the host. Use apx discover when the task is uncertain, when no native skill clearly fits, or when the task may need non-skill assets.
  • Codex, Gemini, and generic agents: start with apx discover.
  • All targets: 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
apx plugins list

If apx is unavailable, inspect local folders: skills/, commands/, mcp/, agents-md/, hooks/, workflows/.

  1. Match the task to assets.

Prefer the narrowest high-ranked asset whose description matches the current task. Treat apx discover output as a shortlist, not as proof that a powerup has been used.

Examples:

Task signal Asset type to inspect
bug, failing test, regression debugging skill
implementation spec planning skill
file or URL intake file-intake skill
pre-handoff validation command
local MCP setup MCP config
repo instruction baseline AGENTS.md template

Read the full file on GitHub · 127 lines

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 · 127 lines · 43 tokens per session scan A e2ec2900e994

Subscribe to this mod's changes

using-powerups is a skill published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,145 once invoked, about $0.0002 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-14.