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 RoninForge/budgetclawnpx agentmods add plugins/roninforge/budgetclaw/plugingit clone --depth 1 https://github.com/RoninForge/budgetclawGrade A, and why
budgetclaw 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": "budgetclaw",
"version": "0.1.0",
"description": "Zero-key Claude Code cost tracking, per project and per branch. Budget caps with SIGTERM enforcement, reads your local ~/.claude session logs, and syncs to a hosted team dashboard (Goei).",
"author": {
"name": "RoninForge",
"url": "https://github.com/RoninForge"
},
"homepage": "https://roninforge.org",
"repository": "https://github.com/RoninForge/budgetclaw",
"license": "MIT",
"keywords": [
"spend-monitor",
"budget",
"cost",
"claude-code",
"telemetry",
"claude-ai",
"ccusage",
"cost-tracking",
"usage-tracking",
"token-usage",
"claude-code-analytics",
"claude-tracker",
"claude-max",
"claude-subscription",
"cost-dashboard",
"ai-spend",
"llm-cost",
"multi-machine",
"team",
"burn-rate"
],
"skills": "./skills/",
"hooks": "./hooks/hooks.json"
}
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 · 37 lines scan A b246417b86e1
budgetclaw is a plugin published in the GitHub repository RoninForge/budgetclaw (8 stars, last pushed 2d 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-31.
Other plugins, from other repositories
agents-blockchain-web3
Specialized agents for blockchain development, smart contracts, and Web3 applications.
crucible
Stress-test a high-stakes decision with a council of up to 17 personas that debate, rebut, and return a verdict. For product direction, strategy, and career calls where being wrong is expensive.
pm-dev
Shipping discipline for PMs who code: TDD workflow, pre-commit verification loop, security review, research-before-build.
abcd-marketplace
Plugin marketplace listing 1 plugin: abcd.
sync-agents-settings
Plugin marketplace listing 1 plugin: sync-agents-settings.
prompt-chime
Cross-platform notification toolkit — get alerted when prompts complete with customizable sounds, toast notifications, profiles, and quiet hours.