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/recordnpx skills add bromso/metapowers --skill recordgit 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/record)<a href="https://agentmods.dev/skills/bromso/metapowers/record"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/record.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.00008 | $0.00398 |
| Opus 5 | $0.00004 | $0.00199 |
| Sonnet 5 | $0.00002 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
record 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 3d 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
Record
Capture and log all financial transactions for "$ARGUMENTS". Document each transaction with date, amount, parties, description, and source document reference.
Prerequisites
None — this is the first phase.
Process
-
Identify transaction sources:
- What accounts are active? (bank, credit card, cash, digital payments)
- What period are we recording? (month, quarter, year)
- What source documents are available? (receipts, invoices, bank feeds, contracts)
-
Capture each transaction:
- Date — when the transaction occurred
- Amount — exact figure with currency
- Direction — inflow (revenue, loan) or outflow (expense, payment)
- Counterparty — who paid or was paid
- Description — what the transaction was for
- Source — receipt number, invoice ID, or bank reference
- Payment method — bank transfer, card, cash, etc.
-
Organize the transaction log:
- Sort chronologically
- Flag any transactions missing source documents
- Note any unusual or large transactions for review
- Identify recurring transactions (subscriptions, rent, payroll)
-
Write the artifact to
.metapowers/bookkeeping/$ARGUMENTS/01-record.mdwith sections:- Period — date range covered
- Transaction Log — table of all transactions
- Missing Documents — transactions without source references
- Flags — unusual items requiring review
Output
The transaction log written to .metapowers/bookkeeping/$ARGUMENTS/01-record.md. Present a summary highlighting:
- Total transactions recorded
- Total inflows and outflows
- Any missing documents or flagged items
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.
- 3d ago First seen · 47 lines · 8 tokens per session scan A 6526f6d2b263
record 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 398 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
laravel-billing
Use when implementing subscriptions, invoices, payment methods, webhooks, or billing portals with Laravel Cashier (Stripe or Paddle).
laravel-stripe-connect
Use when implementing multi-vendor marketplace payments, seller onboarding, commissions, payouts, or split payments with Stripe Connect.
better-auth
Use when implementing Next.js authentication with Better Auth — OAuth, 2FA, magic links, SSO, Stripe billing, or session management.
rust-core-language
Use when writing or reviewing idiomatic Rust — edition 2024 ownership/borrowing design, or fixing LLM pitfalls (clone tax, unwrap infestation, indexed loops). Not for error-type design (rust-error-handling) or SOLID layout (solid-rust).
evolve
Research-driven multi-cycle improvement director. Forms causal hypotheses about why scores are low, validates them with scout agents before attacking, dispatches axis-parallel fleet attacks, extracts transferable patterns, and runs indefinitely within a budget envelope. Accumulates a persistent belief model and…
business-growth-consultant
Finds the single constraint currently limiting a business's growth and the highest-leverage moves against it, rather than producing a list of everything that could be improved. Use this when growth has stalled or slowed, when deciding where to spend limited time or budget, when revenue rises but profit does not, when…