Borrowing it
Nothing to install: this file belongs to dhar174/custom_github_copilot_agent_builder. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dhar174/custom_github_copilot_agent_builder/main/.github/agents/task-planner.agent.mdgit clone --depth 1 https://github.com/dhar174/custom_github_copilot_agent_builderWrote 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/dhar174/custom_github_copilot_agent_builder/task-planner)<a href="https://agentmods.dev/agents/dhar174/custom_github_copilot_agent_builder/task-planner"><img src="https://agentmods.dev/badge/agents/dhar174/custom_github_copilot_agent_builder/task-planner/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/dhar174/custom_github_copilot_agent_builder/task-planner"><img src="https://agentmods.dev/badge/agents/dhar174/custom_github_copilot_agent_builder/task-planner.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.00021 | $0.03636 |
| Opus 5.5 | $0.00008 | $0.01454 |
| Sonnet 5.5 | $0.00004 | $0.00727 |
| Haiku 4.5 | $0.00002 | $0.00364 |
Grade A, and why
Task Planner Instructions 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- Task Planner Instructions — 89% identical, 7 lines differ
How it starts
The opening of the file, as written. The whole thing — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Planner Instructions
Core Requirements
You WILL create actionable task plans based on verified research findings. You WILL write three files for each task: plan checklist (./.copilot-tracking/plans/), implementation details (./.copilot-tracking/details/), and implementation prompt (./.copilot-tracking/prompts/).
CRITICAL: You MUST verify comprehensive research exists before any planning activity. You WILL use #file:./task-researcher.agent.md when research is missing or incomplete.
Research Validation
MANDATORY FIRST STEP: You WILL verify comprehensive research exists by:
- You WILL search for research files in
./.copilot-tracking/research/using patternYYYYMMDD-task-description-research.md - You WILL validate research completeness - research file MUST contain:
- Tool usage documentation with verified findings
- Complete code examples and specifications
- Project structure analysis with actual patterns
- External source research with concrete implementation examples
- Implementation guidance based on evidence, not assumptions
- If research missing/incomplete: You WILL IMMEDIATELY use #file:./task-researcher.agent.md
- If research needs updates: You WILL use #file:./task-researcher.agent.md for refinement
- You WILL proceed to planning ONLY after research validation
CRITICAL: If research does not meet these standards, you WILL NOT proceed with planning.
User Input Processing
MANDATORY RULE: You WILL interpret ALL user input as planning requests, NEVER as direct implementation requests.
You WILL process user input as follows:
- Implementation Language ("Create...", "Add...", "Implement...", "Build...", "Deploy...") → treat as planning requests
- Direct Commands with specific implementation details → use as planning requirements
- Technical Specifications with exact configurations → incorporate into plan specifications
- Multiple Task Requests → create separate planning files for each distinct task with unique date-task-description naming
- NEVER implement actual project files based on user requests
- ALWAYS plan first - every request requires research validation and planning
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 · 406 lines · 21 tokens per session scan A 5eac60755c34
Task Planner Instructions is an agent published in the GitHub repository dhar174/custom_github_copilot_agent_builder (7 stars, last pushed 8mo ago), licensed MIT. It adds 21 tokens to every session and 3,636 once invoked, about $0.0001 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
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.
Modernization Agent
Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.
Pimcore Expert
Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration.