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 commands/cputester5465/countbean-plugin/assessgit clone --depth 1 https://github.com/CPUtester5465/countbean-pluginWrote 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/cputester5465/countbean-plugin/assess)<a href="https://agentmods.dev/commands/cputester5465/countbean-plugin/assess"><img src="https://agentmods.dev/badge/commands/cputester5465/countbean-plugin/assess.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.00027 | $0.00721 |
| Opus 5 | $0.00014 | $0.00360 |
| Sonnet 5 | $0.00005 | $0.00144 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
assess 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 4d 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.
Review the user's book and report findings. Focus, if given: $ARGUMENTS
Call assess_book and report what it returns. Do not do your own arithmetic on the ledger.
The tool computes every figure, and it computes them carefully — which months are complete,
whether there is enough data for a run rate, what counts as unusual for a given account. Those
decisions are the difference between a report and a guess.
The rules, in order of how much damage breaking them does
-
sufficient: falsemeans you do not have the number. It is not a number with a caveat. Say what is missing and what would fix it — usually "another month or two of recording". Never estimate around it, never say "roughly" or "on track for". -
Only complete months are averaged. The tool marks each month
complete. The current month is almost never complete, and including it makes spending look like it fell in every category. Report the current month as its own line, clearly labelled as still in progress. -
State the window. Every finding is about
coverage.first_datetocoverage.last_date. A reader who does not know the window cannot judge anything you say. -
An outlier is not an error.
outliersare postings large relative to their own account. The annual insurance premium lands here every year and is correct. Present them as "worth a look", never as mistakes, and never imply fraud. -
posting_countis postings, not transactions. One transaction has at least two. Do not call it a transaction count. -
Do not advise on tax, or tell the user what to do with their money. Describe what the book shows. If they ask what to do about it, answer as a bookkeeper would — what the numbers mean — and suggest their accountant for anything that turns on jurisdiction or intent.
Shape of the report
Lead with the window and one honest sentence about what the data can support. Then:
- Where the money went — top categories from
categories, with shares. Group the long tail. - What changed —
moversbetween the two named complete months.pct_change: nullwithnote: "new this month"means a new category, not infinite growth. - Run rate — from
run_rateifsufficient, always withmonths_used. If it carries arunway_months, quoterunway_notealongside it: it assumes the next months look like the last ones, which is an assumption and should be said out loud. - Worth a look —
outliers, with the account's own median for context. - Gaps —
data_quality. These are the findings the user can act on immediately, and uncategorised spending makes every category figure above it less trustworthy, so say so.
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.
- 4d ago First seen · 53 lines · 27 tokens per session scan A dad587dcbffc
assess is a command published in the GitHub repository CPUtester5465/countbean-plugin (46 stars, last pushed 9d ago), licensed MIT. It adds 27 tokens to every session and 721 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-30.
Other commands, from other repositories
report
Command "report" from rustledger/rustledger, covering rledger report, usage, subcommands, global options and examples.
price
Command "price" from rustledger/rustledger, covering title: rledger price description: fetch commodity prices, rledger price, usage, arguments and options.
add
Command "add" from rustledger/rustledger, covering rledger add, usage, arguments, options and interactive mode.
format
Command "format" from rustledger/rustledger, covering rledger format, usage, arguments, options and examples.
index
Command "index" from rustledger/rustledger, covering commands reference, commands, global options, specifying the ledger file and explicit file path.
extract
Command "extract" from rustledger/rustledger, covering rledger extract, usage, arguments, options and config-based import.