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 compliance-scoregit 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/compliance-score)<a href="https://agentmods.dev/skills/bromso/metapowers/compliance-score"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/compliance-score/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/compliance-score"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/compliance-score.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.00008 | $0.00572 |
| Opus 5 | $0.00004 | $0.00286 |
| Sonnet 5 | $0.00002 | $0.00114 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
compliance-score 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compliance Score
Calculate the overall compliance score for "$ARGUMENTS" across all assessed regulations, providing a weighted scorecard with per-regulation breakdowns and trend analysis.
Prerequisites
None — this is a utility skill.
Process
-
Read context files:
- Read
plugins/compliance/shared/grc-lifecycle-guide.mdfor GRC methodology reference - Read all assessment files from
.metapowers/compliance/$ARGUMENTS/01-assess/if they exist - Read
.metapowers/compliance/$ARGUMENTS/00-scope.mdfor compliance priorities and weights (if available)
- Read
-
Per-regulation scoring:
- For each regulation with an assessment: count controls by status — compliant, partially compliant, non-compliant, not applicable
- Calculate percentage compliance score per regulation
- Partially compliant controls count as 50% compliant
- Not applicable controls are excluded from the denominator
- Document the scoring methodology transparently
-
Weighted overall score:
- If compliance priorities exist (from Phase 0): use business importance weights
- If no priorities exist: weight equally across all assessed regulations
- Calculate weighted overall compliance score
- Present as percentage with confidence indicator (based on assessment completeness)
-
Analysis:
- Identify weakest areas — regulations or control domains with lowest scores
- Identify strongest areas — regulations where compliance is highest
- Calculate gap-to-target — how much improvement is needed to reach target score (e.g., 90%)
- If previous scores exist: show trend analysis (improving, stable, declining)
-
Scorecard presentation:
- Overall weighted score with RAG rating
- Per-regulation score with RAG rating
- Per-domain score (access control, data protection, incident response, etc.)
- Comparison to industry benchmarks where available
-
Present scorecard to user with:
- Overall Compliance Score — weighted score with confidence level
- Per-Regulation Breakdown — individual regulation scores
- Weakest Areas — domains and regulations needing the most attention
- Strongest Areas — domains and regulations in good standing
- Trend Analysis — improvement over time (if previous data exists)
- Gap-to-Target — effort needed to reach compliance goals
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 · 61 lines · 8 tokens per session scan A 751747b6a14f
compliance-score is a skill published in the GitHub repository bromso/metapowers (1 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 572 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
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…