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 skills/bromso/metapowers/reportnpx skills add bromso/metapowers --skill reportgit 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/skills/bromso/metapowers/report)<a href="https://agentmods.dev/skills/bromso/metapowers/report"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/report.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.00009 | $0.00462 |
| Opus 5 | $0.00005 | $0.00231 |
| Sonnet 5 | $0.00002 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
report 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.
What it actually says
Report
Generate a comprehensive accessibility audit report for "$ARGUMENTS" with executive summary, detailed findings, and prioritized remediation steps.
Prerequisites
Read .metapowers/accessibility/$ARGUMENTS/02-evaluate.md. If this file does not exist, tell the user:
Phase 2 (Evaluate) has not been completed for "$ARGUMENTS". Run
/accessibility:evaluate $ARGUMENTSfirst, or use--skip-checksto bypass.
If --skip-checks is present in $ARGUMENTS, skip this check and log to .metapowers/accessibility/$ARGUMENTS/skip-log.md.
Process
-
Read context files:
- Read
.metapowers/accessibility/$ARGUMENTS/01-scope.mdfor audit scope - Read
.metapowers/accessibility/$ARGUMENTS/02-evaluate.mdfor discovered issues - Read
plugins/accessibility/shared/audit-report-template.mdfor output structure - Read
plugins/accessibility/shared/remediation-patterns.mdfor fix guidance
- Read
-
Create executive summary:
- Overall conformance status
- Total issues by severity
- Key findings in plain language
- Business impact assessment
-
Document detailed findings:
- For each issue: description, WCAG criterion, severity, location, impact, remediation steps
- Include code examples (before/after) where applicable
- Group by WCAG principle for easy navigation
-
Prioritize remediation:
- Critical issues first (blocking access)
- Then major issues (significant barriers)
- Then minor issues (enhancements)
- Estimate effort for each fix (quick fix vs. significant rework)
-
Write the artifact to
.metapowers/accessibility/$ARGUMENTS/03-report.mdfollowing the audit report template.
Output
The audit report written to .metapowers/accessibility/$ARGUMENTS/03-report.md. Present a summary to the user highlighting:
- Conformance status
- Top priority issues to fix
- Estimated remediation effort
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 · 50 lines · 9 tokens per session scan A c0446672ce4d
report is a skill published in the GitHub repository bromso/metapowers (1 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 462 once invoked, about $0.0000 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 skills, from other repositories
design-method
Use when starting any design task — resolves register, sets the 3 dials, locks Gate 0, and routes to the right move and target skill.
design-webapp
Use when building or extending a dashboard, SaaS screen, or any authenticated app surface — use design-web instead for a marketing site.
design-web
Use when building or revising a marketing/landing/campaign page, register brand locked at Gate 0 — use design-webapp for app screens instead.
fusecore
Use when creating modules, understanding FuseCore structure, or implementing features in a FuseCore modular-monolith Laravel project.
laravel-architecture
Use when structuring a Laravel project, creating services/repositories/actions, implementing dependency injection, or organizing code layers.
laravel-auth
Use when implementing user authentication, API tokens, social login, or authorization in Laravel 13.