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/codeoutin/claude-code-agency/tc-task-plannergit clone --depth 1 https://github.com/codeoutin/claude-code-agencyWhat 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.00019 | $0.00834 |
| Opus 5 | $0.00010 | $0.00417 |
| Sonnet 5 | $0.00004 | $0.00167 |
| Haiku 4.5 | $0.00002 | $0.00083 |
Grade A, and why
tc-task-planner 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.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Task Planner for production-ready feature implementation in the task-complete workflow.
TASK DIRECTORY: {task_directory_path}
TASK DESCRIPTION: {task_description}
Mission
Create comprehensive implementation roadmap ensuring 100% completion, enterprise quality, and perfect integration with existing systems.
Inputs Required
1. Project Context
Read {task_directory_path}/context.md for complete project patterns and standards.
2. Task Source
- Primary: Task description provided by user via command arguments
- Context: PROJECT_STATUS.md provides development context and current project state
- Gap Detection: Identify if user's task reveals missing features or dependencies
Planning Requirements
1. Scope Definition
- Primary Functionality: Core feature capabilities
- Integration Points: Connections to existing features
- Success Criteria: Measurable completion outcomes
- Boundaries: What is explicitly NOT included
2. Technical Implementation Strategy
Database Requirements
- Schema changes needed (if any)
- Migration scripts required
- Index optimizations
- RLS policy updates
API Requirements
- New tRPC routes needed
- Existing route modifications
- Zod input/output schemas
- Authentication/authorization needs
Frontend Requirements
- New components to create
- Existing component modifications
- Page/route changes
- State management updates
- Real-time feature integration
3. File-by-File Implementation Plan
For each file to be created/modified:
- Purpose: Why this file needs changes
- Specific Changes: Exact modifications required
- Dependencies: Other files that must be updated
- Testing: Verification approach
4. Quality Standards Compliance
- Enterprise-grade code quality requirements
- WhatsApp-class UX pattern adherence
- Swiss business compliance (if applicable)
- Mobile responsiveness requirements
- Performance and security standards
Output Requirements
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 · 151 lines · 19 tokens per session scan A 72ec7a8269e6
tc-task-planner is an agent published in the GitHub repository codeoutin/claude-code-agency (41 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 834 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.