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/statusgit clone --depth 1 https://github.com/CPUtester5465/countbean-pluginWhat 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.00022 | $0.00142 |
| Opus 5 | $0.00011 | $0.00071 |
| Sonnet 5 | $0.00004 | $0.00028 |
| Haiku 4.5 | $0.00002 | $0.00014 |
Grade A, and why
status 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
Call the book_status tool and present the result to the user clearly: book name and location,
operating currency, number of accounts, net worth (assets + liabilities), net income, and the
list of recent commits. If no book exists yet, tell them to run /countbean:init.
If the user asked a specific question in $ARGUMENTS (e.g. "how much did I spend on food?"),
answer it by calling run_query or balances with an appropriate BQL filter rather than only
showing the summary.
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 · 12 lines · 22 tokens per session scan A 5e61028b63dd
status is a command published in the GitHub repository CPUtester5465/countbean-plugin (17 stars, last pushed 7d ago), licensed MIT. It adds 22 tokens to every session and 142 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.
review
Kernel first (/ledger-verify or /ledger-audit), then host TDD/review/security if present. See skills/ledger-review/SKILL.md.