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/bromso/metapowers/claude-mdgit clone --depth 1 https://github.com/bromso/metapowersWrote 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/bromso/metapowers/claude-md)<a href="https://agentmods.dev/instructions/bromso/metapowers/claude-md"><img src="https://agentmods.dev/badge/instructions/bromso/metapowers/claude-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.1 | $0.00749 | $0.00749 |
| Opus 5 | $0.00375 | $0.00375 |
| Sonnet 5 | $0.00150 | $0.00150 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
metapowers CLAUDE.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 5d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Metapowers
Structured, repeatable workflows for digital production domains. 288 skills across 16 plugins.
Architecture
- Monorepo: Bun + Turborepo workspaces
- Plugins (
plugins/): Each domain is a plugin with SKILL.md files, hooks, and shared resources - Packages (
packages/): CLI (create-metapowers), skill-validator, scoring-harness, figma-mcp - Docs (
apps/docs/): Fumadocs + Next.js static site deployed to GitHub Pages
Plugin Structure
Every plugin follows this pattern:
plugins/<domain>/
├── .claude-plugin/plugin.json # Plugin manifest
├── hooks/hooks.json # Quality gate hooks
├── shared/ # Templates and reference docs
└── skills/<skill-name>/SKILL.md # One SKILL.md per skill
SKILL.md Format
---
description: Verb-first description under 200 chars
---
# Skill Name
What the skill does with "$ARGUMENTS" placeholder.
## Prerequisites
What must exist before running (or "None").
## Process
Numbered steps with clear instructions.
## Output
Where the artifact is written and what to present.
Conventions
- Descriptions start with a verb: "Create", "Analyze", "Review" — enforced by skill-validator
- Artifacts: All stored in
.metapowers/<domain>/<project>/with numbered prefixes (01-, 02-, etc.) - Commits: Conventional commits (
feat(domain):,fix(docs):,docs:,ci:) - Formatting: Biome for linting and formatting (
bun run check,bun run format) - Testing: Vitest for packages (
bun run test) - Skill validation:
bun run lint:skillsvalidates all 288 SKILL.md files
Commands
bun run build # Build all packages
bun run test # Run tests
bun run lint:skills # Validate all SKILL.md files
bun run check # Biome lint check
bun run format # Biome auto-format
bun run changeset # Create a changeset for npm release
Adding a New Domain
- Create
plugins/<domain>/following the structure above - Add plugin.json with name, description, author
- Create SKILL.md files in
skills/<name>/SKILL.md - Add to
.claude-plugin/marketplace.json - Create docs in
apps/docs/content/docs/<domain>/ - Add to
apps/docs/content/docs/meta.jsonsidebar - Run
bun run lint:skillsto validate
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.
- 5d ago First seen · 89 lines · 749 tokens per session scan A f2a145800c3d
metapowers CLAUDE.md is an instructions file published in the GitHub repository bromso/metapowers (1 stars, last pushed 4mo ago), licensed MIT. It adds 749 tokens to every session, about $0.0037 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
agent-smith CLAUDE.md
Instructions for cyijun/agent-smith, covering claude.md, project overview, project structure, development workflow and installing the skill for testing.
agentic-validation-skills CLAUDE.md
Claude Code instructions for vivekkrishna/agentic-validation-skills, covering agentic test automation guidelines (cige), 1. establish context before testing, 2. anchor every test to intent, 3. define guardrails before executing and 4. treat execution as adaptive guidance.
ccplugins CLAUDE.md
Claude Code instructions for emaballarin/ccplugins, a project described as: ✨ Personal plugins for Claude Code (& friends)... maybe worth sharing!
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.