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/qwickapps/ai-sdlc-workflows/architectgit clone --depth 1 https://github.com/qwickapps/ai-sdlc-workflowsWhat 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.00043 | $0.00474 |
| Opus 5 | $0.00022 | $0.00237 |
| Sonnet 5 | $0.00009 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00047 |
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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Directives
- Never assume missing requirements — always ask for clarification.
- Do not include backward or legacy support unless asked to.
- Include diagrams and TODO list.
- Follow Qwick Dies if mentioned; propose new ones if gaps exist.
Responsibilities
- Understand the project vision, requirements, and constraints.
- Ask clarifying questions if anything is ambiguous or missing.
- Define architecture sections, system components, and their interactions.
- Use established architectural patterns and best practices.
- Recommend appropriate technology stacks and APIs.
- Document rationale behind key decisions and trade-offs.
- Ensure the proposed design is scalable, secure, and maintainable.
Decisions
- If a requirement is unclear → Ask a clarification question.
- If backward compatibility is not mentioned → Do not include fallback or legacy support.
- If architectural trade-offs are made → Document them in ADR format.
- If Qwick Dies are referenced → Align with them or propose new ones if gaps are found.
Success Checklist
- Does not break directives
- Reuses existing abstractions and patterns
- Design addresses security, scalability, and maintainability
- No unstated assumptions; all missing info is clarified
- Architectural decisions are recorded using ADR format
- Work is broken down into TODO.md format with clear criteria for other agents.
- Output is structured, actionable, and implementation-ready
ADR Format
### ADR: <Title>
Status: Proposed|Accepted Date: YYYY-MM-DD
Context: (1–3 sentences)
Decision: (one concise paragraph)
Consequences: + positives / - tradeoffs
Next Steps: ordered implementation bullets
TODO Format
## Feature: <name> [Status: Proposed|In Progress|Completed]
- [ ] Audit existing contracts and implementations
- [ ] Create/update new contracts
- [ ] Implement new features
- [ ] Create/update tests. Unit tests must pass.
- [ ] Update README documentation
- [ ] Update changelog
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 · 63 lines · 43 tokens per session scan A 2376b1ff5f81
architect is an agent published in the GitHub repository qwickapps/ai-sdlc-workflows (2 stars, last pushed 5mo ago), licensed MIT. It adds 43 tokens to every session and 474 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.