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.
npx agentmods add instructions/yeaight7/agent-powerups/agents-mdgit 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/instructions/yeaight7/agent-powerups/agents-md)<a href="https://agentmods.dev/instructions/yeaight7/agent-powerups/agents-md"><img src="https://agentmods.dev/badge/instructions/yeaight7/agent-powerups/agents-md.svg" alt="Measured on agentmods" 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 | $0.00643 | $0.00643 |
| Opus 5 | $0.00321 | $0.00321 |
| Sonnet 5 | $0.00129 | $0.00129 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
agent-powerups AGENTS.md 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 3d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
Agent Powerups is a Node.js/TypeScript CLI plus a catalog of agent assets. Core CLI code lives in src/cli/, with command handlers in src/cli/commands/ and shared helpers in src/cli/utils/. Tests live in test/ as *.test.ts.
Shipped assets are organized by type: skills/, commands/, hooks/, mcp/, agents-md/, workflows/, and examples/. Repository docs live in docs/. Keep catalog.json in sync whenever a shipped asset is added, renamed, removed, or materially changed.
Build, Test, and Development Commands
npm install: install Node dependencies.npm run build: compile TypeScript withtscand create theapxwrapper.npm run test: build, then run the Node test suite viascripts/run-node-tests.mjs.apx doctor: run local health checks after building.apx list: inspect catalog entries.python scripts/validate-skills.py: validate skill metadata and required files.python scripts/validate-catalog.py: validatecatalog.json.python scripts/validate-mirrors.py: validate that plugin skill copies match their root skills (variant allowlist inside the script).python scripts/check-requirements.py: check documented tool requirements.
Coding Style & Naming Conventions
Use TypeScript ES modules targeting Node 20+. The project uses strict TypeScript, NodeNext modules, semicolons, double quotes, and two-space indentation. Prefer small named functions, explicit error messages, and local helpers in src/cli/utils/ when logic is shared.
Use kebab-case for asset folders and catalog names, for example skills/systematic-debugging/. Every skill folder must include SKILL.md with YAML frontmatter containing name and description. Agent instruction files should use YAML frontmatter plus a pure Markdown body with headings, not XML-like tags as normal top-level sections.
Testing Guidelines
Add or update focused tests in test/*.test.ts for CLI behavior and validation logic. Use npm run test for the full test path. For asset-only changes, also run the relevant Python validators. There is no separate coverage gate; cover changed behavior and edge cases directly.
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.
- 3d ago First seen · 40 lines · 643 tokens per session scan A 5c76e677eb85
agent-powerups AGENTS.md is an instructions file published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 643 tokens to every session, about $0.0032 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-08-31.
Other instructions, from other repositories
kodama AGENTS.md
Instructions for amergrgic/kodama, covering agents, architecture, agent roster, conventions and validation.
enozunu AGENTS.md
Instructions for tooppoo/enozunu, covering instructions, worktree, pull request, review-sized implementation and skill usage.
Skill-HQE AGENTS.md
Instructions for spearchucker667/Skill-HQE, covering agents.md, hqe skill — agent operating instructions, purpose, 1. mission and 2. repository identity.
enozunu CLAUDE.md
Instructions for tooppoo/enozunu, covering instructions, worktree, pull request, review-sized implementation and skill usage.
open-agents AGENTS.md
AGENTS.md instructions for vercel-labs/open-agents, covering agents.md, quick links, authentication, database & migrations and environment isolation.
notfair-plugin AGENTS.md
AGENTS.md instructions for nowork-studio/notfair-plugin, covering notfair — skill resolver for ai agents, how to use this file, seo, paid ads and analytics.