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/scopenpx skills add bromso/metapowers --skill scopegit 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/scope)<a href="https://agentmods.dev/skills/bromso/metapowers/scope"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/scope.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.00009 | $0.00373 |
| Opus 5 | $0.00005 | $0.00187 |
| Sonnet 5 | $0.00002 | $0.00075 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
scope 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.
What it actually says
Scope
Define the accessibility audit scope for "$ARGUMENTS". Determine what to test, which WCAG level to target, and what pages or features to include.
Prerequisites
None — this is the first phase.
Process
-
Understand the audit target:
- What is "$ARGUMENTS"? A website, app, component, feature, or page?
- Ask the user to clarify if ambiguous
-
Define the scope:
- Which pages or features to test (sample representative pages)
- Which WCAG level to target (A, AA, or AAA — recommend AA as baseline)
- Any specific compliance requirements (Section 508, EN 301 549, EAA)
- Any known accessibility concerns to prioritize
-
Identify testing approach:
- Automated testing: code analysis, ARIA validation, contrast checks
- Manual testing: keyboard navigation, screen reader flow, focus management
- Content review: alt text quality, heading structure, link text
-
Write the artifact to
.metapowers/accessibility/$ARGUMENTS/01-scope.mdwith sections:- Target — what's being audited
- WCAG Level — target conformance level
- Pages/Features — specific items to test
- Compliance Requirements — applicable standards
- Testing Methods — automated + manual approach
- Known Concerns — pre-existing issues to prioritize
Output
The audit scope written to .metapowers/accessibility/$ARGUMENTS/01-scope.md. Present a summary to the user highlighting:
- Scope boundaries
- Target WCAG level
- Testing approach
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 · 44 lines · 9 tokens per session scan A 36bb9e12f9ea
scope 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 373 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
building
Implementation skill for writing production code with TDD. Covers the RED-GREEN-REFACTOR cycle, false-RED detection, vertical slicing, scope escalation, test process discipline, and code generation patterns. Loaded by component-builder and bug-investigator.
memory-and-handoff
Two-mode skill: (1) session memory — load/persist durable workflow state under .cc10x/ (activeContext, patterns, progress) so context survives compaction; (2) handoff package — portable, secrets-redacted export for a coworker, different tool, or fresh non-cc10x session.
plan-review-gate
Use after saving a non-trivial plan or decision RFC when a fail-closed feasibility, completeness, and alignment review must block execution.
cc10x-guide
Answers questions about cc10x itself — what it is, how to install and configure it, how the router, workflows, memory, and hooks operate, and how to troubleshoot. Use this skill when: the user asks ABOUT cc10x — "what is cc10x", "how do I configure cc10x", "why isn't cc10x activating", "how do cc10x workflows work"…
codebase-design
Canonical deep-module vocabulary (module, interface, depth, seam, adapter, leverage, locality) for designing a module's shape — a lot of behaviour behind a small interface at a clean seam, testable through that interface. The single source of truth for these terms; other skills (architecture, codebase-hygiene…
verification
Verification discipline: task completion is not goal achievement. Covers the gate function, self-critique gate, validation levels, evidence array protocol, and goal-backward lens. Loaded by integration-verifier, component-builder, and bug-investigator.