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/auditnpx skills add bromso/metapowers --skill auditgit 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)<a href="https://agentmods.dev/skills/bromso/metapowers/audit"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/audit.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.00011 | $0.00470 |
| Opus 5 | $0.00005 | $0.00235 |
| Sonnet 5 | $0.00002 | $0.00094 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
audit 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 5d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit
Audit specific accounts or transactions for "$ARGUMENTS". Examine supporting documentation, test balances, and identify discrepancies or irregularities.
Prerequisites
None — utility skill, run anytime. More effective when ledger data is available from Phase 3 or later.
Process
-
Define audit scope:
- Which accounts or transaction types are being audited?
- What period is covered?
- What is the audit objective? (accuracy, completeness, existence, valuation, disclosure)
- What materiality threshold applies?
-
Gather evidence:
- Pull account balances and transaction details from the ledger
- Request supporting documentation (invoices, contracts, confirmations)
- Identify the population and select a sample (statistical or judgmental)
-
Perform audit procedures:
- Vouching — trace recorded transactions back to source documents (tests existence/occurrence)
- Tracing — trace source documents forward to recorded transactions (tests completeness)
- Recalculation — independently recalculate key amounts
- Confirmation — verify balances with third parties (banks, customers, vendors)
- Analytical procedures — compare to expectations, prior periods, or industry benchmarks
-
Document findings:
- For each finding, record:
- Condition — what was found
- Criteria — what was expected
- Cause — why the discrepancy exists
- Effect — financial impact
- Recommendation — corrective action
- For each finding, record:
-
Write the artifact to
.metapowers/accounting/$ARGUMENTS/audit.mdwith sections:- Audit Scope & Objectives — what was audited and why
- Procedures Performed — tests conducted and samples selected
- Findings — each finding with condition, criteria, cause, effect, recommendation
- Conclusion — overall assessment of account accuracy and reliability
Output
The audit written to .metapowers/accounting/$ARGUMENTS/audit.md. Present a summary highlighting:
- Number of findings by severity
- Total financial impact of discrepancies
- Key recommendations
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.
- 5d ago First seen · 53 lines · 11 tokens per session scan A af321bb26a99
audit 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 470 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
laravel-stripe-connect
Use when implementing multi-vendor marketplace payments, seller onboarding, commissions, payouts, or split payments with Stripe Connect.
chief-financial-officer
Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on. Use this to build or challenge a budget, model a decision's financial consequence, assess unit economics or runway, evaluate an investment or spend request, set financial controls…
fundraising-and-investor-relations
Raises capital and manages the relationship afterward — deciding how much and why, understanding what dilution and preferences actually cost, running a process with real competitive tension, preparing for diligence before it starts, and reporting to investors and a board in a way that keeps support when results are…
financial-statement-analysis
Reads a set of financial statements and establishes what changed and why — fluctuation analysis against prior period and against budget, profitability, liquidity, solvency and efficiency ratios, benchmarking, and the non-GAAP measures presented alongside them. Use this to interpret results, review a counterparty's or…
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…
payroll-operations
Runs the pay cycle so it is right, on time, and provable — the calendar and cutoffs, what feeds pay from the HRIS and time systems, gross-to-net and the deductions in it, multi-jurisdiction registration and tax filing, off-cycle payments and corrections, and the reconciliation to the general ledger. Use this to design…