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.
/plugin marketplace add CPUtester5465/countbean-pluginnpx agentmods add plugins/cputester5465/countbean-plugin/plugingit clone --depth 1 https://github.com/CPUtester5465/countbean-pluginGrade A, and why
countbean 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 yesterday.
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
{
"name": "countbean",
"description": "Hosted plain-text accounting for Claude Code. Initialise a git-backed Beancount cloud book, let Claude ingest bank statements and receipts into validated double-entry transactions, and generate HTML/Excel reports.",
"version": "0.5.3",
"author": {
"name": "Countbean"
},
"homepage": "https://github.com/CPUtester5465/countbean-plugin",
"repository": "https://github.com/CPUtester5465/countbean-plugin",
"keywords": [
"accounting",
"beancount",
"fava",
"finance",
"mcp",
"bookkeeping"
]
}
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.
- yesterday First seen · 19 lines scan A d31385203489
countbean is a plugin published in the GitHub repository CPUtester5465/countbean-plugin (17 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
ledger
Execution as Proof for money — the deterministic correctness layer AI agents call. Exact Money.from (no floats), kernel-enforced double-entry via JournalEntry + validateEntry + Ledger.apply, audit-hashed ledgers, canon citations. Provides /ledger- skills and slash commands.
ledger
Execution as Proof for money — the deterministic correctness layer AI agents call. Exact Money.from (no floats), kernel-enforced double-entry via JournalEntry + validateEntry + Ledger.apply, audit-hashed ledgers, canon citations. Provides /ledger- skills and slash commands.
claude-for-accounting
Agent-native accounting engagement plugins — throw client documents at the agent for bookkeeping through MPERS financial statements, QC, tax, and finalisation. Umbrella install: accounting-engagement. Maintainer: Hazli Johar .
accounting-engagement
One-install umbrella for throw-work accounting agents: full engagement pipeline, all stage skills synced from modular plugins, SessionStart resume hook, and artifact schemas.
beancount-ledger
Beancount as system-of-record ledger and Fava as the interactive UI. Export finalized journals to .beancount, validate with bean-check, open Fava for P&L/BS exploration.
bookkeeping-accounting
Record sales, purchases, receipts, payments and journals; classify every transaction against the chart of accounts; produce balancing journal entries.