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 accounts-payablegit 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/accounts-payable)<a href="https://agentmods.dev/skills/bromso/metapowers/accounts-payable"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/accounts-payable/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/accounts-payable"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/accounts-payable.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.00010 | $0.00395 |
| Opus 5 | $0.00005 | $0.00198 |
| Sonnet 5 | $0.00002 | $0.00079 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
accounts-payable 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.
What it actually says
Accounts Payable
Process vendor invoices and schedule payments for "$ARGUMENTS". Track what is owed, when it is due, and optimize payment timing.
Prerequisites
None — utility skill, run anytime.
Process
-
Collect outstanding invoices:
- Gather all unpaid vendor invoices
- Record: vendor name, invoice number, date, due date, amount, terms
- Note any early payment discounts (e.g., 2/10 net 30)
-
Verify each invoice:
- Match invoice to purchase order or contract
- Confirm goods/services were received
- Check for duplicate invoices
- Flag discrepancies for dispute
-
Build payment schedule:
- Sort by due date
- Prioritize based on: terms, discounts, vendor relationships, cash position
- Group payments by payment run (weekly, biweekly)
- Calculate cash needed per payment run
-
Track aging:
- Current (0-30 days)
- 31-60 days
- 61-90 days
- Over 90 days
- Flag overdue items for immediate action
-
Write the artifact to
.metapowers/bookkeeping/$ARGUMENTS/accounts-payable.mdwith sections:- Outstanding Invoices — table of all unpaid invoices
- Payment Schedule — upcoming payments by date
- Aging Report — amounts by aging bucket
- Discount Opportunities — savings available from early payment
- Disputes — invoices under review
Output
The accounts payable report written to .metapowers/bookkeeping/$ARGUMENTS/accounts-payable.md. Present a summary highlighting:
- Total outstanding payables
- Upcoming payment obligations
- Available early payment discounts
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 · 52 lines · 10 tokens per session scan A 19fd0fa09798
accounts-payable 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 395 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…