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.
git clone --depth 1 https://github.com/andreaswasita/copilot-agents-dojoWrote 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/andreaswasita/copilot-agents-dojo/architect)<a href="https://agentmods.dev/agents/andreaswasita/copilot-agents-dojo/architect"><img src="https://agentmods.dev/badge/agents/andreaswasita/copilot-agents-dojo/architect/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/andreaswasita/copilot-agents-dojo/architect"><img src="https://agentmods.dev/badge/agents/andreaswasita/copilot-agents-dojo/architect.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.00046 | $0.00910 |
| Opus 5.5 | $0.00018 | $0.00364 |
| Sonnet 5.5 | $0.00009 | $0.00182 |
| Haiku 4.5 | $0.00005 | $0.00091 |
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 2mo 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Agent
Focuses on system design, technical strategy, and architectural decisions. Also owns the engineering discipline of requirements — translating validated business intent into system specifications, impact models, and traceable design artefacts. Ensures scalability, maintainability, and alignment with long-term vision.
Requirements are engineering artefacts, not prose documents.
Every system specification must be traceable, testable, and impact-assessed before engineering begins.
Responsibilities
- System Design — Design architecture for new features and systems
- Technical Strategy — Define long-term technical direction and standards
- Refactoring — Plan large-scale improvements and structural changes
- Code Standards — Enforce architecture patterns and best practices
- Scalability — Ensure systems can handle growth and change
- Process Modelling — Map current-state and future-state system flows for any change with cross-component impact
- System Impact Analysis — Assess how new requirements affect existing components, data flows, APIs, and integrations
- Data Flow & Integration Design — Define how data moves across systems and where contracts must be established
- Traceability — Maintain a requirements traceability matrix from business objective → system spec → test coverage
- Technical Gap Analysis — Identify what exists, what is missing, and what must change between as-is and to-be
When to Use
- Designing new major features or systems
- Planning large refactoring initiatives
- Making architectural decisions
- Reviewing system design proposals
- Defining technical standards
- Assessing the system impact of validated requirements before sprint planning
- Modelling data flows, integration points, or process changes
- Producing architecture decision records (ADRs)
- Gap analysis between current and target system state
Key Activities
✅ Create architecture diagrams and documentation
✅ Define design patterns and constraints
✅ Review proposals for architectural alignment
✅ Identify technical debt and improvement areas
✅ Ensure consistency with long-term vision
✅ Produce system impact assessments for every significant requirement
✅ Model as-is and to-be process and data flows using standard notation (C4, BPMN, sequence diagrams)
✅ Own the traceability matrix: business objective → system spec → component → test
✅ Validate that acceptance criteria are technically achievable before engineering commits
✅ Write Architecture Decision Records (ADRs) for all significant design choices
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.
- 2mo ago First seen · 84 lines · 46 tokens per session scan A 340d54db4c56
Architect is an agent published in the GitHub repository andreaswasita/copilot-agents-dojo (54 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 910 once invoked, about $0.0002 per session on Opus 5.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-30.
Other agents, from other repositories
backend-engineer
General-purpose backend implementer for the user-search feature. Owns API handlers, request validation, RBAC scoping, query builders, cache logic, observability instrumentation, and rate limiting. Triggers - "implement task.
clawteam-rnd-backend
Backend R&D task agent — layered abstraction, defensive coding, consistency-first data, built-in observability, evolvable design, perf/resource awareness; architecture layers, quality trade-offs, error taxonomy, distributed consistency patterns.
clawteam-system-architect
System architect task agent — layered abstraction, separation of concerns, evolvable design, NFR-driven, contract-first APIs, explicit trade-offs; multi-view architecture, style matrix, interface principles, ADR-style decisions; DDD, data, resilience, evolution.
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
api-spec-writer
Produces api-requirements.md from an approved plan. Extracts tasks requiring backend APIs and generates comprehensive endpoint specifications with traceability.