agentmods.dev

config

config is a command for Claude Code from TeamManagementPlugin/claude-plugin. It costs 12 tokens per session (3,281 once invoked), scanned A, original, MIT.

A guided command for changing non-secret settings for the team-management system.

In plain words
What is it for?
Use it to view current settings and update supported configuration values through a guided menu.
Why use it?
It helps users review and update configuration without putting API tokens or other secrets into the command session.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions CLAUDE.md; names the AskUserQuestion tool; mentions Codex.

Part of the team-management plugin — 9 commands, 17 agents, 6 hooks, 1 MCP server shipped together

not rated 6repo changed yesterday A scan 12 tokens original MIT

Good fit Use it to view current settings and update supported configuration values through a guided menu.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/teammanagementplugin/claude-plugin/config
View source ↗ TeamManagementPlugin/claude-plugin team.management
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.

Clone the repo
git clone --depth 1 https://github.com/TeamManagementPlugin/claude-plugin

Made for: Claude Code.

Or install team-management, the plugin that ships this one along with the rest of its 9 commands, 17 agents, 6 hooks, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for config

README.md
[![agentmods](https://agentmods.dev/badge/commands/teammanagementplugin/claude-plugin/config/github.svg)](https://agentmods.dev/commands/teammanagementplugin/claude-plugin/config)
Your own site
<a href="https://agentmods.dev/commands/teammanagementplugin/claude-plugin/config"><img src="https://agentmods.dev/badge/commands/teammanagementplugin/claude-plugin/config/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for config

Your own site · 80×15
<a href="https://agentmods.dev/commands/teammanagementplugin/claude-plugin/config"><img src="https://agentmods.dev/badge/commands/teammanagementplugin/claude-plugin/config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,281 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.03281
Opus 5.5 $0.00005 $0.01312
Sonnet 5.5 $0.00002 $0.00656
Haiku 4.5 $0.00001 $0.00328

Measured yesterday against content hash b414d90b1214, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

plugin/commands/config.md · 208 lines

How it starts

The opening of the file, as written. The whole thing — 208 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

  1. Show current settings. Call mcp__plugin_team-management_tm__config_get and 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 a schema array — the authoritative list of every settable key with its type, any allowed enum values, and a one-line description. Treat it as ground truth: consult it for a key's exact type/enum before every config_update call rather than guessing, and never try to set a key absent from schema (those are either secrets — set in the token file — or engine-managed state).

  2. Check agy's global permission rules BEFORE walking the sections. If config_get shows agy enabled (agy.enabled true and "agy" in ai_providers.enabled_providers), show the global-write disclosure from section 5 below now, not later. The write can happen in ANY config_update call while the rules are missing — including one that only changes developer_name — so binding the disclosure to a section the user might skip means a write to another tool's global config with nothing shown. After any write, the response carries agy_permission_rules: "written" means the rules were added to ~/.gemini/antigravity-cli/settings.json; say so plainly. "unchanged" needs no mention.

Read the full file on GitHub · 208 lines

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.

  1. yesterday Changed · +54 lines b414d90b1214
  2. 1mo ago First seen · 154 lines · 12 tokens per session scan A aaa9eb9c0fa9

Subscribe to this mod's changes

config is a command published in the GitHub repository TeamManagementPlugin/claude-plugin (6 stars, last pushed 2d ago), licensed MIT. It adds 12 tokens to every session and 3,281 once invoked, about $0.0000 per session on Opus 5.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.

Claude CodeProject managementagentic-workflowsai-agentsanthropicclaudeclaude-plugin
Related

Other commands, from other repositories

save

Save current work state for next session. Creates/updates .planning/ files (CHECKPOINT.md, STATE.md, settings.json) so Heimdall resumes with full context. NOT a rewind — saves forward progress. Run before closing a session or at any milestone.

randomittin/heimdall · 55 tokens

status

Show current Heimdall state — project phase, active agents, quality gates, conflicts.

randomittin/heimdall · 19 tokens

loops

Weekly review — surface everything in-flight and force a ship / block / kill decision on each.

loganhc-09/claude-chief-of-staff · 19 tokens

p4-sprint

Plans the current sprint: pulls matching stories from the backlog, defines the sprint goal, identifies risks, and creates the sprint document. Called repeatedly at the start of each new sprint.

jonase47/ccpr · 0 tokens

p4-backlog

Breaks down the features from FEATURES.md into actionable tasks, builds the prioritized backlog, and defines milestones and release planning. The result is BACKLOG.md and PROJECTPLAN.md as the steering foundation for the entire implementation.

jonase47/ccpr · 0 tokens

p5-polish

Collects small clean-up TODOs accumulated during the sprint (from /p5-review, /p5-acceptance, /p5-bugfix, TODO/FIXME comments) that do not justify a full story but make the next sprint easier. Triages each item into polish-now, backlog, handover, or drop. Optionally executes polish-now items directly (TDD mini-cycle…

jonase47/ccpr · 0 tokens