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-prioritiesgit 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-priorities)<a href="https://agentmods.dev/skills/bromso/metapowers/compliance-priorities"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/compliance-priorities/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-priorities"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/compliance-priorities.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.00012 | $0.00596 |
| Opus 5 | $0.00006 | $0.00298 |
| Sonnet 5 | $0.00002 | $0.00119 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
compliance-priorities 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 11d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compliance Priorities
Prioritize the applicable regulations for "$ARGUMENTS" by business impact, enforcement deadlines, and customer demand to determine the optimal compliance sequence.
Prerequisites
None — this is a Phase 0 (Scope) skill.
Process
-
Read context files:
- Read
plugins/compliance/shared/grc-lifecycle-guide.mdfor GRC methodology reference - Read
.metapowers/compliance/$ARGUMENTS/00-scope.mdfor the regulation inventory
- Read
-
Business impact scoring:
- For each applicable regulation, score revenue at risk without certification (0-10)
- Assess deal-blocking potential — how often is this certification requested in sales cycles?
- Estimate market access impact — does non-compliance lock out entire markets or verticals?
-
Urgency scoring:
- Score enforcement deadline proximity (0-10) — active enforcement vs. upcoming vs. future
- Score customer deadline pressure (0-10) — immediate customer requirements vs. nice-to-have
- Flag any regulations with imminent deadlines or recent enforcement actions
-
Effort scoring:
- Score implementation complexity (0-10) — scope of changes needed
- Estimate time to certification (months)
- Assess internal capability gaps — can this be done in-house or requires external help?
-
Priority ranking:
- Calculate weighted priority score (business impact 40%, urgency 35%, inverse effort 25%)
- Rank regulations from highest to lowest priority
- Identify quick wins (high impact, low effort) vs. strategic investments (high impact, high effort)
- Group into tiers: Tier 1 (immediate), Tier 2 (next 6 months), Tier 3 (12+ months)
-
Write the artifact to
.metapowers/compliance/$ARGUMENTS/00-scope.md(append to existing) with sections:- Scoring Matrix — table with impact, urgency, effort, and weighted scores per regulation
- Priority Tiers — Tier 1/2/3 groupings with rationale
- Quick Wins — low-effort, high-impact regulations to tackle first
- Strategic Investments — high-effort certifications that unlock major business value
- Dependencies — regulations that build on each other (e.g., ISO 27001 before CSA STAR)
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.
- 11d ago First seen · 54 lines · 12 tokens per session scan A db88d63cb51d
compliance-priorities is a skill published in the GitHub repository bromso/metapowers (1 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 596 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…
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…
deal-negotiation
Negotiates a commercial deal without giving away the terms that matter — preparing your walk-away and theirs, trading concessions rather than conceding them, recognizing the tactics that create false urgency, protecting price by moving other variables, and closing on terms someone can actually deliver. Use this to…
capital-structure-and-covenants
Decides how the business is financed and what that financing then requires of it — debt versus equity, weighted average cost of capital as a hurdle rate, how much leverage cash flow can carry, and the financial, affirmative and negative covenants, definitions, test dates and cure rights that come attached. Use this to…