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 Metabuilder-Labs/tokenjamnpx agentmods add plugins/metabuilder-labs/tokenjam/plugingit clone --depth 1 https://github.com/Metabuilder-Labs/tokenjamGrade A, and why
tokenjam 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": "tokenjam",
"displayName": "TokenJam",
"description": "Local-first observability and cost control for Claude Code agents: a zero-token statusline showing context re-read %, savings/optimize reports, and a health check. Runs 100% locally against your own telemetry, no signup or network account required.",
"version": "0.6.11",
"author": {
"name": "Anil Murty",
"email": "[email protected]",
"url": "https://tokenjam.dev"
},
"homepage": "https://tokenjam.dev",
"repository": "https://github.com/Metabuilder-Labs/tokenjam",
"license": "MIT",
"keywords": [
"cost-optimization",
"observability",
"statusline",
"opentelemetry",
"tokens",
"context-window",
"agents"
]
}
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 · 24 lines scan A 0666558f3d88
tokenjam is a plugin published in the GitHub repository Metabuilder-Labs/tokenjam (106 stars, last pushed 3d 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
goalkeeper
Durable goal-following for Claude Code: contracts with definition-of-done, subagent judge gates, and linear chains.
trigger-tree
See which docs your AI actually discovers — local documentation telemetry for Claude Code.
polisade-marketplace
Plugin marketplace listing 1 plugin: polisade.
milestone-driver
Drives a GitHub milestone to completion: triages each issue for design gaps + dependency order up front, then for each buildable issue finds the root cause (or parks it), dispatches a TDD implementer subagent, runs unit + E2E tests + code review, opens a PR, and auto-merges issues on CI green. The whole loop sits…
shiploop
Single-plugin marketplace for shiploop — a self-improving multi-agent harness (every resolved ticket writes a lesson into your git-tracked CLAUDE.md) that grinds your ticket backlog across every repo in your product.
cc-autopilot
Autonomous judge agents fix your app's debt, build what's missing, and verify every change through a browser or gate suite before it lands, then find the next thing and keep going until you say stop. Each fixer owns a file-disjoint slice of the tree, so no two can ever collide, and nothing unverified reaches git. A…