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 audit-readinessgit 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/audit-readiness)<a href="https://agentmods.dev/skills/bromso/metapowers/audit-readiness"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/audit-readiness/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/bromso/metapowers/audit-readiness"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/audit-readiness.svg" alt="Reviewed on agentmods" width="80" 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.00011 | $0.00719 |
| Opus 5 | $0.00005 | $0.00360 |
| Sonnet 5 | $0.00002 | $0.00144 |
| Haiku 4.5 | $0.00001 | $0.00072 |
Grade A, and why
audit-readiness 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 9d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Readiness
Assess audit readiness for "$ARGUMENTS" by evaluating evidence completeness, control operating effectiveness, and team preparedness for formal audit engagement.
Prerequisites
Read .metapowers/compliance/$ARGUMENTS/00-scope.md. If this file does not exist, tell the user:
Phase 0 (Scope) has not been completed for "$ARGUMENTS". Run
/compliance:regulatory-landscape $ARGUMENTSfirst, or use--skip-checksto bypass.
If --skip-checks is present in $ARGUMENTS, skip this check.
Process
-
Read context files:
- Read
plugins/compliance/shared/grc-lifecycle-guide.mdfor GRC methodology reference - Read
.metapowers/compliance/$ARGUMENTS/00-scope.mdfor scope and control framework context - Read
.metapowers/compliance/$ARGUMENTS/02-remediate.mdfor control mapping and evidence plan
- Read
-
Evidence completeness check:
- For each regulation being certified: verify all required evidence items are collected
- Check evidence currency — no expired or stale evidence items
- Verify evidence format meets auditor expectations
- Identify evidence gaps — missing, incomplete, or insufficient items
- Calculate evidence completeness percentage per regulation
-
Control operating effectiveness:
- Verify controls have been operating for the required period (typically 3-6 months for SOC 2 Type II, varies by standard)
- Check for control failures or exceptions during the observation period
- Verify compensating controls are documented for any known gaps
- Assess control monitoring — are anomalies being detected and addressed?
-
Mock audit simulation:
- Simulate auditor questions for each control domain
- Verify document requests can be fulfilled within expected timeframes
- Identify areas where explanations would be weak or evidence thin
- Test team knowledge — who answers questions about which controls?
-
Readiness scoring:
- Score each regulation on a readiness scale: Not Ready / Partially Ready / Audit Ready
- Identify remaining gaps or weak areas per regulation
- Create pre-audit remediation punch list with owners and deadlines
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.
- 9d ago First seen · 69 lines · 11 tokens per session scan A 756a180e0d27
audit-readiness is a skill published in the GitHub repository bromso/metapowers (1 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 719 once invoked, about $0.0001 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
chief-legal-and-risk-officer
Owns legal, contracts, intellectual property, regulatory compliance, privacy, security governance, enterprise risk, and audit readiness. Use this to review a contract or commitment, assess regulatory or privacy exposure, evaluate an IP or licensing question, judge the risk in a business decision, prepare for an audit…
chief-human-resources-officer
Owns the organization itself: org design, hiring, performance, compensation, development, culture, and employee relations. Use this to design or restructure a team, plan hiring, write a role or leveling definition, handle a performance or compensation question, diagnose why a team is underperforming for non-technical…
internal-controls-and-audit
Designs and tests controls over financial reporting — segregation of duties, approval limits, evidence, and preparing for audit. Use this to design controls for a process, prepare for an external audit, respond to an audit finding, set approval thresholds, or assess where a small team's segregation of duties is…
disputes-and-legal-holds
Handles a dispute from the first sign of it — recognizing when preservation obligations attach, issuing and scoping a legal hold, suspending automatic deletion across every system that holds relevant material, preserving privilege, managing outside counsel and cost, and evaluating settlement against the real cost of…
intellectual-property
Covers what the organization owns and what it is only borrowing — trademarks and clearance, copyright and work-for-hire, patents and trade secrets, open-source license obligations and copyleft reach, and IP terms in customer, contractor and AI-tool agreements. Use this to check whether a name is usable, establish that…
employment-compliance
Covers the employment rules that carry real penalties — exempt and non-exempt classification, overtime and hours, employee versus contractor status, work authorization and recordkeeping, accommodation requests, and the notices and retention obligations that go with them. Use this to classify a role, review a…