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.
npx agentmods add commands/teammanagementplugin/claude-plugin/configgit clone --depth 1 https://github.com/TeamManagementPlugin/claude-pluginWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00012 | $0.02323 |
| Opus 5 | $0.00006 | $0.01162 |
| Sonnet 5 | $0.00002 | $0.00465 |
| Haiku 4.5 | $0.00001 | $0.00232 |
Grade A, and why
config 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.
How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
team-management: Configure
Guide the user through team-management's non-secret configuration and write it
with the deterministic config_update MCP tool. Secrets (API tokens) are NEVER
set here — they live in the per-project file .claude/state/provider-tokens.json,
which the AI cannot read, and never enter this transcript.
By the time this command runs, the deterministic intent-gate hook has already
written the config session flag (you physically typed the command), so
config_update is unlocked for ~15 minutes. Do NOT pre-authorize config_update
— approve each write when prompted; the per-section batching keeps that to a
handful of prompts.
Workflow
-
Show current settings. Call
mcp__plugin_team-management_tm__config_getand summarise the current config to the user. Token fields appear masked (***set***/***unset***) — that is expected; never ask the user to paste a token here. The response also carries aschemaarray — the authoritative list of every settable key with itstype, anyallowedenum values, and a one-linedescription. Treat it as ground truth: consult it for a key's exact type/enum before everyconfig_updatecall rather than guessing, and never try to set a key absent fromschema(those are either secrets — set in the token file — or engine-managed state). -
State the token-redirect up front:
Tokens (GitLab / Jira / GitHub / Telegram) are NOT configured here. Set them in the per-project file
.claude/state/provider-tokens.json— a git-ignored, owner-only (0600) file the AI agent cannot read. It is created for you (with all provider keys blank) the first time you run/team-management:configor start a session; open it in your editor and fill in only the tokens you use. Each project has its own file, so different projects can use different tokens. -
Walk the sections in order, one
AskUserQuestionat a time. For each section, first ask whether the user wants to configure it (offer a clear "skip — leave as-is" option). Skip if not needed. When they do want it, gather the section's values withAskUserQuestion, then make ONEconfig_updatecall for the whole section (batched dotted keys — not one call per field). Section order:
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 · 154 lines · 12 tokens per session scan A aaa9eb9c0fa9
config is a command published in the GitHub repository TeamManagementPlugin/claude-plugin (4 stars, last pushed 26d ago), licensed MIT. It adds 12 tokens to every session and 2,323 once invoked, about $0.0001 per session on Opus 5. 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 commands, from other repositories
research
Research a technical or product question.
brand-setup
Configure a new brand profile with colors, fonts, logo, visual style, platforms, and compliance rules.
save
Save this conversation as a new or existing reusable context.
screens
Structures product UX screen design — inventory, flow, states, and reusable briefs for external design tools — without generating pixels or UI code.
graphify
Turn your vault into a clustered knowledge graph with HTML and JSON outputs.
index
Command "index" from MadaraUchiha-314/the-loop, covering commands, the control plane, daemon commands, repo-scoped commands and maintenance.