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.
git clone --depth 1 https://github.com/WYRE-AI/msp-claude-pluginsWrote 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/commands/wyre-ai/msp-claude-plugins/reconcile-payout)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/reconcile-payout"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/reconcile-payout/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/commands/wyre-ai/msp-claude-plugins/reconcile-payout"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/reconcile-payout.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.00017 | $0.01249 |
| Opus 5 | $0.00009 | $0.00624 |
| Sonnet 5 | $0.00003 | $0.00250 |
| Haiku 4.5 | $0.00002 | $0.00125 |
Grade A, and why
reconcile-payout scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
TOKEN=$(curl -s -X POST "${BASE}/oauth/token" \ How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reconcile Payout
Reconcile a single Alternative Payments payout: retrieve the payout, list every transaction it settled, sum those transactions, confirm the total matches the payout amount, and trace each transaction back to its invoice and customer. This command is entirely read-only.
Prerequisites
- Valid Alternative Payments OAuth2 credentials configured (
AP_CLIENT_ID,AP_CLIENT_SECRET) - Environment selected (
AP_ENVIRONMENT=productionordemo) - Scope
payments:read
Steps
-
Authenticate with Alternative Payments
BASE=https://public-api.alternativepayments.io TOKEN=$(curl -s -X POST "${BASE}/oauth/token" \ -u "${AP_CLIENT_ID}:${AP_CLIENT_SECRET}" \ -H "Content-Type: application/x-www-form-urlencoded" \ -d "grant_type=client_credentials" \ | jq -r '.access_token') -
Retrieve the payout
curl -s "${BASE}/payouts/${PAYOUT_ID}" \ -H "Authorization: Bearer ${TOKEN}" -
List the payout's transactions (cursor-paginated)
curl -s "${BASE}/payouts/${PAYOUT_ID}/transactions?limit=100" \ -H "Authorization: Bearer ${TOKEN}"Loop on
has_more/next_cursor, passingcursor=<next_cursor>per page. -
Sum and compare — total the transaction
amountvalues and compare to the payout'samount. Agreement within rounding = reconciled; otherwise flag a discrepancy. -
Trace each transaction — for each transaction, resolve its
invoice_idandcustomer_idso the deposit can be tied to specific receivables. Optionally fetch the customer name:curl -s "${BASE}/customers/${CUSTOMER_ID}" \ -H "Authorization: Bearer ${TOKEN}" -
Format and return the reconciliation report
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| payout_id | string | Yes | - | Payout id to reconcile |
| show_transactions | boolean | No | true | Include the line-by-line list |
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.
- 10d ago First seen · 181 lines · 17 tokens per session scan A 8df9663881c1
reconcile-payout is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 7d ago), licensed Apache-2.0. It adds 17 tokens to every session and 1,249 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
archive-ledger
../../../shared/commands/archive-ledger.md.
credit-review
Perform credit analysis and risk rating for borrowers or counterparties.
source
Source deals — discover companies and draft founder outreach.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.