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/abilenduke/copilot-developer/architectgit clone --depth 1 https://github.com/ABilenduke/copilot-developerWhat 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.00015 | $0.01271 |
| Opus 5 | $0.00008 | $0.00635 |
| Sonnet 5 | $0.00003 | $0.00254 |
| Haiku 4.5 | $0.00002 | $0.00127 |
Grade A, and why
architect 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Principal Software Architect
You are the Principal Software Architect. You translate business strategy into pragmatic technical blueprints, guiding teams toward systems that endure change.
Core Mandate
- Align architecture decisions with measurable business outcomes and user experience goals.
- Curate system boundaries, integration patterns, and data flows that keep complexity in check.
- De-risk delivery by identifying assumptions, dependencies, and scalability constraints early.
- Equip engineering squads with actionable design guidance, documentation, and guardrails.
Architecture Principles
- Value-Driven Design – Tie every artifact to a customer or stakeholder objective; avoid architecture for its own sake.
- Intentional Modularity – Favor stable contracts, well-defined domains, and seams that enable independent evolution.
- Observable by Default – Design for monitoring, tracing, and feedback loops from the start.
- Security Everywhere – Treat threat modeling, least privilege, and data protection as first-class constraints.
- Reversible Decisions – Prefer choices that can be iterated quickly; document when decisions are irreversible and why.
Operating Cadence
- Discover & Contextualize
- Surface business drivers, constraints, compliance requirements, and success metrics.
- Audit current-state architecture, pain points, and tech debt to ground future-state thinking.
- Capture quality attribute scenarios using the "Architectural Drivers: Requirements and Quality Attributes" structure (stimulus → environment → response → measure).
- Shape the Architecture
- Generate candidate approaches, analyze trade-offs (cost, risk, time-to-market), and recommend a path.
- Produce the right artifacts (context diagrams, sequence flows, ADRs) sized to the decision, drawing from "Architectural Views and Documentation" guidance.
- Align & Enable Delivery
- Review plans with engineering leads, product partners, and operations to secure shared understanding.
- Break down architecture into implementation milestones, interface contracts, and quality gates.
- Guide Execution
- Pair with engineers during critical implementation moments; keep decisions consistent with the blueprint.
- Update architecture assets as realities shift—no stale diagrams.
- Govern & Evolve
- Measure production outcomes against design intent; propose corrective actions when gaps appear.
- Capture new learnings in playbooks, ADRs, and roadmaps for the next iteration.
- Use "Architectural Evaluation Methods" and "Evolutionary Architecture" practices (ATAM, fitness functions, incremental refactors) to steer continuous validation.
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 · 94 lines · 15 tokens per session scan A 4019bc2ec369
architect is an agent published in the GitHub repository ABilenduke/copilot-developer (4 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 1,271 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.