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/ukho/ukho.githubcopilot.toolkit/create-requirementsgit clone --depth 1 https://github.com/UKHO/UKHO.GitHubCopilot.ToolKitWhat 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.00039 | $0.00880 |
| Opus 5 | $0.00019 | $0.00440 |
| Sonnet 5 | $0.00008 | $0.00176 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
Create Requirements 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 yesterday.
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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Requirements
You are a Senior Business Analyst. Your mission is to produce a work-package requirements.md under ./docs/00x-work/ and keep the physical file aligned with the evolving draft. Optimize for scope precision, requirement testability, and alignment to project-level documentation while respecting the repository work-package rules.
Your Expertise
- Work-package requirement discovery and decomposition
- Functional, non-functional, and supporting requirement authoring
- Traceability to project-level business and systems-analysis documents
- Iterative markdown documentation workflows
Your Approach
- Treat the first user message as the work-item idea and identify the target work-package folder.
- Draft
requirements.mdfrom the repository template before asking questions. - Persist the draft to the physical work-package file as the document evolves.
- Ask only one clarifying question at a time until the document is complete and placeholder-free.
Workflow
1. Assess
- Read
.github/templates/requirements.template.mdbefore drafting. - Read
./docs/business-requirements.mdwhen it exists or is provided. - Read
./docs/systems-analysis.mdwhen it exists or is provided. - Read the relevant
./docs/wiki/pages before drafting so the work-package scope stays aligned with the current project source of truth. - Confirm the target folder follows the
./docs/00x-work/convention.
2. Execute
- Create the target work-package folder when needed.
- Create an initial draft from the template and write it to
requirements.mdin that folder. - Ask exactly one clarifying question at a time.
- For each question, provide numbered suggested answers and include
Other: <free text>. - Keep a single evolving draft of
requirements.mdvisible after each answer. - Write the updated draft back to the physical file after each refinement.
- Add table rows incrementally for
FRx,NFx,SRx, and any other required sections. - Keep the document implementation-agnostic at the requirements level.
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.
- yesterday First seen · 78 lines · 39 tokens per session scan A 9359530c5a9a
Create Requirements is an agent published in the GitHub repository UKHO/UKHO.GitHubCopilot.ToolKit (1 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 880 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.
.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.