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 skills add bromso/metapowers --skill retestgit 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/retest)<a href="https://agentmods.dev/skills/bromso/metapowers/retest"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/retest.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.00562 |
| Opus 5 | $0.00005 | $0.00281 |
| Sonnet 5 | $0.00002 | $0.00112 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
retest 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 8d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retest
Verify that accessibility fixes for "$ARGUMENTS" are effective and produce a formal conformance statement.
Prerequisites
Read all prior artifacts. If .metapowers/accessibility/$ARGUMENTS/04-remediate.md does not exist, tell the user:
Phase 4 (Remediate) has not been completed for "$ARGUMENTS". Run
/accessibility:remediate $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 all prior artifacts:
- Read
.metapowers/accessibility/$ARGUMENTS/01-scope.mdfor original scope - Read
.metapowers/accessibility/$ARGUMENTS/02-evaluate.mdfor original issues - Read
.metapowers/accessibility/$ARGUMENTS/03-report.mdfor detailed findings - Read
.metapowers/accessibility/$ARGUMENTS/04-remediate.mdfor fixes applied
- Read
-
Re-evaluate each fixed issue:
- Read the current code for each fixed issue
- Verify the fix resolves the original WCAG violation
- Check for regressions — did the fix break anything else?
- Update issue status: verified fixed, partially fixed, or regression found
-
Run regression checks:
- Re-check all WCAG criteria from the scope
- Verify no new issues were introduced by the fixes
- Check keyboard navigation flow end-to-end
- Verify ARIA attributes are correct
-
Produce conformance statement:
- Overall conformance level achieved
- Per-principle conformance status
- Known remaining issues (if any)
- Recommendations for ongoing maintenance
-
Write the artifact to
.metapowers/accessibility/$ARGUMENTS/05-retest.mdwith sections:- Verification Results — each issue with retest outcome
- Regression Check — any new issues found
- Conformance Statement — formal WCAG conformance declaration
- Remaining Issues — known gaps with justification
- Maintenance Recommendations — ongoing monitoring advice
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.
- 8d ago First seen · 57 lines · 9 tokens per session scan A d64989cce5b5
retest 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 562 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
laravel-testing
Use when testing controllers, services, or models, or implementing TDD on Laravel 13 with Pest 4 / PHPUnit 12.
verification
Use when marking a task complete, finishing a feature, or claiming a bug fixed -- verifies functional resolution before closing. Do NOT use for lint/quality checks (use sniper AFTER this).
go-concurrency
Use when writing or reviewing Go concurrency — goroutines, channels, errgroup, context cancellation, or goroutine leaks. Not for sequential idioms (go-core-idioms).
php-testing
Use when writing/configuring tests on a non-Laravel PHP project — PHPUnit vs Pest. Do NOT use for Laravel test helpers or quality tooling (php-quality-tooling).
react-testing
Testing Library for React 19 - render, screen, userEvent, waitFor, Suspense. Use when writing tests for React components with Vitest.
rust-testing-quality
Use when writing, organizing, or running Rust tests — unit, integration, doc-tests, proptest, criterion benchmarks, or cargo-mutants. Not for CI pipeline wiring (rust-tooling-cicd).