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 agents/teammanagementplugin/claude-plugin/claudegit 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.00000 | $0.03447 |
| Opus 5 | $0.00000 | $0.01724 |
| Sonnet 5 | $0.00000 | $0.00689 |
| Haiku 4.5 | $0.00000 | $0.00345 |
Grade A, and why
CLAUDE 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents Module CLAUDE.md
Purpose
Provides specialized subagents for complex operations in team-management, including multi-provider issue tracking synchronization (GitLab, Jira, GitHub / Gitea), code review, and task management automation.
Narrative Summary
The agents module implements the delegation pattern for team-management, providing specialized subagents that operate in separate context windows to handle complex, file-heavy operations. Each agent is designed for a specific domain of expertise and operates independently to avoid context pollution in the main conversation thread.
With the addition of multi-provider issue tracking integration, the agents module now includes sophisticated synchronization capabilities that handle bidirectional sync between Claude tasks and external issues (GitLab, Jira, GitHub / Gitea), including error recovery, conflict resolution, and batch operations across different providers.
Module Structure
Agent Files
context-gathering.md- Task context manifest creationcontext-refinement.md- Session discovery integrationcode-review.md- Security and quality review; output template includes a## ✨ Strengths (1-3)section before Critical Issues (omit section entirely if nothing genuinely stands out — no performative praise)spec-compliance-reviewer.md- Read-only agent that audits the git diff (including untracked files viagit ls-files --others --exclude-standard) against task Success Criteria. Returns PASS/FAIL verdict with per-criterion coverage breakdown and scope-creep flags; the coverage report is keyed on SC-IDs (SC-1,SC-2, ...) when criteria carry them, falling back to verbatim criterion text for unnumbered/legacy tasks (incl. the## Criteriashort form). Output is structured so the orchestrator can write theSPEC_REVIEW: PASSEDsentinel viaprotocol_save_note, which gates thecode-reviewstep's post_funcrequire_spec_review_passed. Tools: Read, Grep, Glob, Bash.code-cleanliness.md- Code quality and maintainability analysiscode-explorer.md- Existing codebase feature analysis and execution flow tracingcode-architect.md- Architecture design and implementation blueprintslogging.md- Work log consolidation and cleanupservice-documentation.md- CLAUDE.md file maintenancecritic.md- Devil's advocate analysis for proposals and brainstorm topicsuser-perspective.md- End-user impact and UX analysisrisk-security-analyst.md- Combined risk, dependency, and security assessmentscope-strategist.md- Scope definition and implementation phasingcodex-cli.md- Pass-through wrapper agent that shells out to thecodexCLI (codex review --uncommittedfor review,codex exec -s read-onlyfor exec); the caller owns the full prompt. Eachcodexinvocation runs under anenv -i PATH HOMEscrub so pluginuserConfigsecrets are not inherited. Full contract (timeout fallback, sandbox, output shape) in the rootCLAUDE.md"AI Provider Integration".agy-cli.md- Pass-through wrapper agent that shells out to the Google Antigravity (agy) CLI (agy --add-dir "$PWD" --dangerously-skip-permissions --print-timeout 300s -p ...— NO--sandbox, which breaks git on macOS) behind a 330s external watchdog. skip-permissions gets past the headless soft-deny and is CONTAINED by a project-local.agents/hooks.jsonread-only deny-gate (deployed byshared_state.ensure_agy_readonly_gate_deployedwhen agy is enabled); the wrapper preflight-verifies the gate and refuses to run uncontained. Snapshotsgit status/git diff HEADbefore-and-after and prepends anagy review WARNING: agy modified files...line if agy mutated files (detect & report, never auto-revert). Runs under the sameenv -i PATH HOMEscrub; failure surfaces asagy review unavailable: <reason>. Full contract (watchdog fallback, mutation-check details) in the rootCLAUDE.md"AI Provider Integration".- Provider Extensibility: Agent system supports future issue tracking provider 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 · 277 lines · 0 tokens per session scan A c3035dd84a15
CLAUDE is an agent published in the GitHub repository TeamManagementPlugin/claude-plugin (4 stars, last pushed 26d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,447 tokens. 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 agents, from other repositories
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the label strings that actually exist in this repo's issue tracker.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
sweep-scan
You are a backlog sweeper. ./input.json names one repo and the exact source tree to read it against.
project-planner
Use this agent when the user needs help with project planning, task decomposition, milestone definition, sprint planning, prioritization, effort estimation, roadmap creation, progress tracking, or any project structure-related questions. This agent should be used PROACTIVELY whenever the conversation touches on…
durability-arbiter.eval
Boundary scenarios drawn from real usage-retro evidence, each run through the durability-arbiter agent (sonnet). Re-run by spawning the agent with the agent file as prompt + each consultation. First run 2026-06-22: 8/8 correct.
durability-arbiter
Consulted by a running executor at an ambiguous would-stop boundary to decide CONTINUE / ASK / STOP, so the run keeps going autonomously instead of interrupting the user. Plays the user's standing posture with criterion. Read-only and fast.