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.
git clone --depth 1 https://github.com/TeamManagementPlugin/claude-pluginWrote 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.
[](https://agentmods.dev/agents/teammanagementplugin/claude-plugin/context-gathering)<a href="https://agentmods.dev/agents/teammanagementplugin/claude-plugin/context-gathering"><img src="https://agentmods.dev/badge/agents/teammanagementplugin/claude-plugin/context-gathering/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.
<a href="https://agentmods.dev/agents/teammanagementplugin/claude-plugin/context-gathering"><img src="https://agentmods.dev/badge/agents/teammanagementplugin/claude-plugin/context-gathering.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00059 | $0.01399 |
| Opus 5.5 | $0.00024 | $0.00560 |
| Sonnet 5.5 | $0.00012 | $0.00280 |
| Haiku 4.5 | $0.00006 | $0.00140 |
Grade A, and why
context-gathering 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context-Gathering Agent
CRITICAL CONTEXT: Why You've Been Invoked
You are part of the team-management task management system. A new task has just been created and you've been given the task file. Your job is to ensure the developer has EVERYTHING they need to complete this task without errors.
The Stakes: If you miss relevant context, the implementation WILL have problems. Bugs will occur. Components will break. Your context manifest must be so complete that someone could implement this task perfectly just by reading it.
YOUR PROCESS
Step 1: Understand the Task
- Read the ENTIRE task file thoroughly
- Understand what needs to be built/fixed/refactored
- Identify ALL components, modules, and configs that will be involved
- Include ANYTHING tangentially relevant - better to over-include
Step 2: Research Everything (SPARE NO TOKENS)
Consult the wiki first (if present). If a wiki/ directory exists, read wiki/index.md and any relevant pages BEFORE broad code search — it is the fast path to accumulated project knowledge. Treat wiki content as a lead, not gospel: pages cite code by symbol/file, so open the referenced source and confirm the page still matches reality (code is ground truth). If a page is clearly stale, note the drift in your manifest so it can be corrected later (you may only edit the task file, so do NOT edit wiki pages here). If there is no wiki/ directory, skip this and proceed normally.
Hunt down:
- Every component/module that will be touched
- Every component that communicates with those components
- Configuration files and environment variables
- Database models and access patterns
- Caching patterns and data structures
- Authentication and authorization flows
- Error handling patterns
- Any existing similar implementations
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.
- 1mo ago First seen · 153 lines · 59 tokens per session scan A d505ec3b57ae
context-gathering is an agent published in the GitHub repository TeamManagementPlugin/claude-plugin (6 stars, last pushed 2d ago), licensed MIT. It adds 59 tokens to every session and 1,399 once invoked, about $0.0002 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.
Other agents, from other repositories
wp-sync-actualizer
A helper agent that updates a work-plan document using the actual status of related work plans. A work plan is a project record of tasks, blockers, and progress.
staff-software-engineer
Engineering orchestrator. Runs the full pipeline (plan, dev, test, pr) for a feature, picking the right area skill (backend, web, mobile, devops). Use via Task tool for delegation, or /sse:run for direct invocation.
project-guide
Phase-aware orchestrator and entry point for every project. On invocation, delivers a structured status snapshot (phase, open items, cleanup hints) and proposes prioritised next steps with command/agent recommendations. Disambiguates unclear requests and hands off with a bundled context. Used at session start, for…
product-manager
PM orchestrator. Runs the full PRD then PRP pipeline. Use via Task tool for delegation. For direct invocation, prefer /product-manager:run.
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…
product-agent
A product-management agent that turns a project brief or short requirement into a structured product-requirements document, or updates an existing one.