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/anchildress1/awesome-github-copilot/hlbpa-docsgit clone --depth 1 https://github.com/anchildress1/awesome-github-copilotWhat 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.00000 | $0.01213 |
| Opus 5 | $0.00000 | $0.00607 |
| Sonnet 5 | $0.00000 | $0.00243 |
| Haiku 4.5 | $0.00000 | $0.00121 |
Grade A, and why
hlbpa-docs 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HLBPA Agent (High-Level Big-Picture Architect) ✨
View this agent and more in the awesome-copilot repository on GitHub.
NOTE: XML-supported agent versions have been removed to reduce maintenance. Use the Markdown-based custom agent format going forward.
Why Use HLBPA? ❓
- Rapidly understand complex repos.
- Auto‑generate API & data flow diagrams.
- Highlight missing tests or docs.
- Identify architectural gaps and risks.
- Get a visual overview of recent changes.
What Does HLBPA Actually Do? 🤔
HLBPA is your AI-powered architectural documentation assistant. It helps you quickly understand the big picture of any codebase, then guides you through the details as needed. Here’s what you can expect as a user:
- Starts with the big picture: HLBPA begins by mapping out the major components, data flows, and interfaces in your system. You get a high-level overview first.
- Drills down as needed: If the architecture is complex or you want more detail, HLBPA automatically creates focused diagrams and documentation for subsystems, interfaces, or even specific files. You can always ask it to narrow or expand the scope.
- No code or tests generated: HLBPA is strictly for documentation. It won’t write code or tests—just docs, diagrams, and gap scans.
- Accessible, modern diagrams: All diagrams are in Mermaid format, with accessibility tags for screen readers. Large diagrams are split up for clarity, and you’ll find them in
docs/diagrams/. - Everything in Markdown: All output is GitHub Flavored Markdown (GFM), so it’s easy to read, share, and edit. Even if you ask for a Confluence-style doc, you’ll get a Markdown version that looks the part.
- Iterative gap scan: HLBPA doesn’t stop at the first pass. It will surface missing info, mark unknowns as
TBD, and ask you for clarifications in a single batch at the end. This way, you can answer all questions at once and get a complete doc in fewer steps. - You control the scope: By default, HLBPA documents the whole repo. But you can target a folder, subsystem, or file—just specify what you want. If you don’t, it will drill down as needed to make the architecture clear.
- RAI Attribution: Every document ends with a footer showing it was generated by GitHub Copilot as directed by you.
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.
- 3d ago First seen · 85 lines · 0 tokens per session scan A 0cce65703579
hlbpa-docs is an agent published in the GitHub repository anchildress1/awesome-github-copilot (65 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,213 tokens. 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-30.
Other agents, from other repositories
workflow-orchestrator
Agent "workflow-orchestrator" from Poorgramer-Zack/copilot-mcp-tool, covering example dialogue, user, agent response, after user confirmation and upon completion.
Custom Agent Foundry
Expert at designing and creating VS Code custom agents with optimal configurations.
C#/.NET Janitor
Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.
oss-growth-hacker
OSS adoption and growth-hacking specialist for microsoft/apm. Activate for README/docs conversion work, launch tactics, contributor funnel, story angles, and to feed reviewed changes into the maintained growth strategy at WIP/growth-strategy.md.
apm-primitives-architect
Use this agent to design or critique APM agent primitives -- skills, agents, instructions, and gh-aw workflows under .apm/ and .github/. Activate when authoring new primitives, refactoring existing skill bundles, designing multi-agent orchestration, or assessing whether a primitive change adheres to PROSE and Agent…
deep-review-orchestrator
Use this agent when the user asks to perform a comprehensive deep review using multiple competing AI models. Trigger phrases include: 'perform a deep review with multiple perspectives' 'get competing reviews of these changes' 'conduct a thorough review using different models' 'review these changes with multiple LLMs'…