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/certification-trackernpx skills add bromso/metapowers --skill certification-trackergit 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/certification-tracker)<a href="https://agentmods.dev/skills/bromso/metapowers/certification-tracker"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/certification-tracker.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.00010 | $0.00660 |
| Opus 5 | $0.00005 | $0.00330 |
| Sonnet 5 | $0.00002 | $0.00132 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade A, and why
certification-tracker 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 4d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Certification Tracker
Track certification status, validity periods, and renewal dates for "$ARGUMENTS" to ensure continuous compliance and timely renewal of all certifications.
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 applicable regulations - Read
.metapowers/compliance/$ARGUMENTS/03-certify.mdfor audit readiness and certification status
- Read
-
Create certification register:
- For each regulation/standard: record certification status (not started, in progress, certified, expired)
- Certificate date — when certification was granted
- Expiry date — when certification expires
- Renewal lead time — how far in advance to begin renewal process
- Surveillance audit dates — for standards requiring periodic surveillance (ISO)
- Renewal requirements — what is needed for renewal vs. initial certification
- Assigned owner — who is responsible for maintaining this certification
-
Maintenance requirements:
- Document between-audit requirements per certification
- Continuous monitoring evidence needed
- Management reviews required (frequency, participants)
- Internal audit requirements
- Corrective action tracking from previous audits
-
Calendar and reminders:
- Set calendar reminders for: renewal start dates, surveillance audits, evidence collection deadlines, management review due dates
- Identify overlapping audit periods — consolidation opportunities
- Flag certifications approaching expiry within 6 months
-
Status dashboard:
- Create at-a-glance view of all certification statuses
- RAG (Red/Amber/Green) rating per certification
- Days until next audit or renewal
- Outstanding actions from previous audits
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.
- 4d ago First seen · 65 lines · 10 tokens per session scan A f15d950170ca
certification-tracker is a skill published in the GitHub repository bromso/metapowers (1 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 660 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
researchers-legal
Researches court documents, indictments, plea agreements, and sentencing records. Use when the album subject involves legal proceedings or criminal cases.
prior-art-search
Systematic 7-step methodology for comprehensive patent prior art searches and patentability assessments using BigQuery and CPC classification.
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.
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.
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.
debugging
Debugging discipline: feedback loop FIRST, root cause before fix, blast radius after fix. Covers the 10-rung construction ladder, LSP-powered tracing, hypothesis quality criteria, and four-phase investigation. Loaded by bug-investigator.