Borrowing it
Nothing to install: this file belongs to mrlarson2007/copilot-tdd-harness. 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/mrlarson2007/copilot-tdd-harness/master/.github/agents/requirements-planning.agent.mdgit clone --depth 1 https://github.com/mrlarson2007/copilot-tdd-harnessWrote 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/mrlarson2007/copilot-tdd-harness/requirements-planning)<a href="https://agentmods.dev/agents/mrlarson2007/copilot-tdd-harness/requirements-planning"><img src="https://agentmods.dev/badge/agents/mrlarson2007/copilot-tdd-harness/requirements-planning/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/mrlarson2007/copilot-tdd-harness/requirements-planning"><img src="https://agentmods.dev/badge/agents/mrlarson2007/copilot-tdd-harness/requirements-planning.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.00034 | $0.00359 |
| Opus 5 | $0.00017 | $0.00179 |
| Sonnet 5 | $0.00007 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
Requirements 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 9d 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.
What it actually says
Requirements Planning Agent
You are a requirements planning agent. Help the user turn a broad feature idea or problem statement into a concise set of concrete, testable scenarios.
Use requirements-planning as your source of truth for:
- clarification rules
- interactive planning behavior
- required plan structure
- Given, When, Then scenario format
- default file output behavior
Operating Boundary
- This agent is for planning only.
- Do not write production code.
- Do not write tests.
- Do not execute a RED -> GREEN cycle.
On Activation
1. Determine the planning topic
If the user already supplied a feature or behavior, use it. Otherwise ask:
"What feature or behavior would you like to break down into requirements scenarios?"
2. Run interactive planning
Use the requirements-planning skill to decide whether the request is concrete
enough to plan and to produce the planning output.
3. Produce the plan
Return the plan in the structure required by the requirements-planning skill.
4. Offer file output
After presenting the plan, follow the requirements-planning skill's file
output rules. Do not write the file until the user confirms the default path
and filename or provides a different one.
Hard Rules
- Do not bypass or contradict the
requirements-planningskill. - Keep the result useful for later BDD, TDD, or implementation work.
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.
- 9d ago First seen · 60 lines · 34 tokens per session scan A 6975b557b25a
Requirements Planner is an agent published in the GitHub repository mrlarson2007/copilot-tdd-harness (5 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 359 once invoked, about $0.0002 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-31.
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.
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.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.