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 All-The-Vibes/TokenMasterXnpx agentmods add plugins/all-the-vibes/tokenmasterx/token-master-plugingit clone --depth 1 https://github.com/All-The-Vibes/TokenMasterXGrade A, and why
token-master 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.
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": "token-master",
"description": "Token-efficient code-understanding harness. Routes structural questions (callers, callees, impact, inheritors) to a prebuilt code graph instead of repeated grep and file-reads, cutting cumulative context tokens. Type /token-master in a repo to build the index and turn on routing.",
"version": "0.1.0",
"author": {
"name": "Shyam Sridhar"
},
"homepage": "https://github.com/shyamsridhar123/TokenMasterX",
"repository": "https://github.com/shyamsridhar123/TokenMasterX",
"license": "MIT",
"keywords": ["tokens", "context", "code-graph", "routing", "efficiency"],
"skills": ["skills/"]
}
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.
- 2d ago First seen · 14 lines scan A 51a5247f5fef
token-master is a plugin published in the GitHub repository All-The-Vibes/TokenMasterX (3 stars, last pushed 25d 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
reposkein
Deterministic code-graph MCP server: structural navigation, semantic find, impact analysis, and architecture decision records for the current repo. Zero infrastructure — the graph lives in .reposkein/ and the indexer binary is fetched on first run.
context-engineering-protocol
Source-cited, human-approved context packages (code graph + requirements + conventions) for AI coding agents -- assembled before a generation task runs, not guessed at afterward.
aidd-context
Knowledge production: project bootstrap, project init, context generation, mermaid diagrams, learn, discovery.
wordcount-habitat
The wordcount team's habitat packaged as a plugin: CLAUDE.md skeleton, HARNESS.md constraint set, the spec-implement orchestrator command, the wordcount-style skill, and the standard CI workflow. Adopt with /wordcount-habitat-init.
kage
Kage manages your memory and agents. It briefs and runs agents in isolated git worktrees for a single run or a multi-wave goal, re-runs the checks itself instead of trusting the agent's report, and remembers what it learns so each brief is smarter than the last.
aria-knowledge
ARIA — Applied Reasoning and Insight Architecture. Persistent human-governed knowledge for Claude Code via a five-phase lifecycle: capture → govern → promote → apply → refresh. Stages session insights/decisions/feedback into review backlogs, promotes approved items to a tag-indexed markdown base, and applies them via…