budgetary

Install

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.

Security

Grade A, and why

budgetary 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 2d 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.

clients/claude-code/.claude-plugin/plugin.json · 22 lines

What it actually says

{
  "name": "budgetary",
  "displayName": "Budgetary",
  "version": "0.0.0",
  "description": "Pre-flight, probabilistic token-spend estimate (range, scenario, confidence) for a coding task.",
  "author": {
    "name": "Thriftell",
    "url": "https://github.com/thriftell"
  },
  "license": "Apache-2.0",
  "homepage": "https://api.budgetary.tools",
  "repository": "https://github.com/thriftell/budgetary-clients",
  "userConfig": {
    "api_key": {
      "type": "string",
      "title": "Budgetary API key",
      "description": "API key used to authenticate the Budgetary estimate tool and the session-end actuals submission. Starts with bg_live_ or bg_test_.",
      "sensitive": true
    }
  }
}

Contents

What it installs

The manifest is a name and a version. 1 skill, 1 hook, 1 MCP server travel with it, and installing the plugin installs all of them — 39 tokens a session between them. Each is measured on its own page, and each can be installed alone.

Changes

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.

Related

Other plugins, from other repositories