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/KIMISKI33/awesome-copilotWrote 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/kimiski33/awesome-copilot/task-planner)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/task-planner"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/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/kimiski33/awesome-copilot/task-planner"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/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.03499 |
| Opus 5 | $0.00010 | $0.01750 |
| Sonnet 5 | $0.00004 | $0.00700 |
| Haiku 4.5 | $0.00002 | $0.00350 |
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 7d 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.
This is a copy
89% identical to Task Planner Instructions — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 405 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.
- 7d ago First seen · 405 lines · 21 tokens per session scan A 396e333df431
Task Planner Instructions is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 4d ago), licensed MIT. It adds 21 tokens to every session and 3,499 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to Task Planner Instructions, differing in 7 lines, and is treated as a copy.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…