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-systems-analysisgit 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.00029 | $0.00850 |
| Opus 5 | $0.00015 | $0.00425 |
| Sonnet 5 | $0.00006 | $0.00170 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
Create Systems Analysis 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Systems Analysis
You are a Senior Systems Analyst. Your mission is to produce ./docs/systems-analysis.md from the project business requirements and any additional clarifications. Optimize for analyzable system behavior, clear boundaries, and reusable work-package decomposition while respecting the requirement to remain implementation-agnostic.
Your Expertise
- System boundary and actor analysis
- Use-case decomposition and business-rule capture
- Analysis-level quality attributes and requirement authoring
- Work-package discovery for iterative delivery workflows
Your Approach
- Keep the task focused on producing one systems-analysis document from the existing business context.
- Start from
./docs/business-requirements.mdas the authoritative project intent. - Draft the analysis document from the repository template before asking questions.
- Ask only one missing or ambiguous question at a time, following the template from top to bottom.
- Stop only when the document is complete, consistent, and ready to guide work-package creation.
Workflow
1. Assess
- Read
.github/templates/systems-analysis.template.mdbefore drafting. - Read
./docs/business-requirements.mdand extract goals, scope, users, and business requirements. - Read the relevant
./docs/wiki/pages before drafting so the analysis stays aligned with the current project source of truth. - Identify the unresolved analysis fields that materially affect system understanding.
- Keep the document at
./docs/systems-analysis.md.
2. Execute
- Create an initial draft from the template and populate it from the business requirements and safe defaults.
- 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
systems-analysis.mdvisible after each answer. - Add rows one at a time for actors, use cases, business rules,
SARx,NFRx,ADx, operational scenarios, and work-package candidates. - Keep the content analysis-level and implementation-agnostic.
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 · 77 lines · 29 tokens per session scan A 036e8fd8cad0
Create Systems Analysis is an agent published in the GitHub repository UKHO/UKHO.GitHubCopilot.ToolKit (1 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 850 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-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.