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/moshcoder/moshcodeWrote 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/moshcoder/moshcode/rate)<a href="https://agentmods.dev/commands/moshcoder/moshcode/rate"><img src="https://agentmods.dev/badge/commands/moshcoder/moshcode/rate/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/moshcoder/moshcode/rate"><img src="https://agentmods.dev/badge/commands/moshcoder/moshcode/rate.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.00016 | $0.00435 |
| Opus 5.5 | $0.00006 | $0.00174 |
| Sonnet 5.5 | $0.00003 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
rate 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 1mo 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
Task
billing rate $ARGUMENTS --json
With no arguments this lists every rate. set, show and rm take a target,
which is either a client handle or default.
The spec
A price, then any of these in any order:
- a period:
hour,day(8h),week(40h),month(160h),project,task - a unit that gets multiplied:
agent,seat,person,team upto:Nto cap the multiplier,min:Nfor a minimum billed period
$400/hour/agent/upto:4 means four agents cost sixteen hundred an hour, and so do
six. 0.5 SOL/day, 250 USDC/task and $5000/project all parse too.
Rules
- Do not set or change a rate unless the user asked. This is the number in somebody's contract.
- Read
describesback to them when confirming — it is the rate as a sentence, and it is how you catch a spec that parsed differently from how it was meant. - Settlement (
--prefer SOL --accept fiat) is deliberately separate from the price. The number in the contract does not change because the rail did, so do not "convert" a rate to a preferred ticker. - A price given in a ticker invoices in that ticker. Do not turn
0.5 SOLinto a dollar figure: nobody computed that number. - If a spec is rejected, the error names the words that are allowed. Fix the spec rather than falling back to a bare number, which would silently mean "per hour, flat".
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.
- 1mo ago Changed 42ea5feade55
- 1mo ago First seen · 41 lines · 16 tokens per session scan A 462d338a08f4
rate is a command published in the GitHub repository moshcoder/moshcode (3 stars, last pushed 4d ago), licensed MIT. It adds 16 tokens to every session and 435 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
merit-reconcile
Preview or check the status of Stripe → Merit payout reconciliation (read-only).
cost-per-task
Compute cost-per-successful-task unit economics from usage and cost data, including retries, failures, and quality thresholds.
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
scan
Scan AWS account for cost optimization.
audit
Scan for non-kernel money math. Rebuild critical flows as JournalEntrys. Replay and prove. Complements /ledger-verify.