spec-kit-token-budget

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

spec-kit-token-budget 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.

.claude/settings.json · 34 lines

What it actually says

{  "permissions": {
    "allow": [
      "WebSearch",
      "WebFetch",
      "Bash(.specify/scripts/bash/**)",
      "Bash(ls**)",
      "Bash(cat**)",
      "Bash(find**)",
      "Bash(grep**)",
      "Bash(awk**)",
      "Bash(date**)"
    ],
    "deny": [],
    "ask": [],
    "defaultMode": "auto"
  },
  "statusLine": {
    "type": "command",
    "command": "./.claude/statusline.sh",
    "padding": 1
  },
  "extraKnownMarketplaces": {
    "nx-claude-plugins": {
      "source": {
        "source": "github",
        "repo": "nrwl/nx-ai-agents-config"
      }
    }
  },
  "enabledPlugins": {
    "nx@nx-claude-plugins": true
  }
}

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 settings, from other repositories