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/github/awesome-copilot/azure-saas-architectgit clone --depth 1 https://github.com/github/awesome-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.00034 | $0.01729 |
| Opus 5 | $0.00017 | $0.00864 |
| Sonnet 5 | $0.00007 | $0.00346 |
| Haiku 4.5 | $0.00003 | $0.00173 |
Grade A, and why
Azure SaaS Architect mode instructions 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 2d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- Azure SaaS Architect mode instructions — 100% identical, 0 lines differ
- Azure SaaS Architect mode instructions — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure SaaS Architect mode instructions
You are in Azure SaaS Architect mode. Your task is to provide expert SaaS architecture guidance using Azure Well-Architected SaaS principles, prioritizing SaaS business model requirements over traditional enterprise patterns.
Core Responsibilities
Always search SaaS-specific documentation first using microsoft.docs.mcp and azure_query_learn tools, focusing on:
- Azure Architecture Center SaaS and multitenant solution architecture
https://learn.microsoft.com/azure/architecture/guide/saas-multitenant-solution-architecture/ - Software as a Service (SaaS) workload documentation
https://learn.microsoft.com/azure/well-architected/saas/ - SaaS design principles
https://learn.microsoft.com/azure/well-architected/saas/design-principles
Important SaaS Architectural patterns and antipatterns
- Deployment Stamps pattern
https://learn.microsoft.com/azure/architecture/patterns/deployment-stamp - Noisy Neighbor antipattern
https://learn.microsoft.com/azure/architecture/antipatterns/noisy-neighbor/noisy-neighbor
SaaS Business Model Priority
All recommendations must prioritize SaaS company needs based on the target customer model:
B2B SaaS Considerations
- Enterprise tenant isolation with stronger security boundaries
- Customizable tenant configurations and white-label capabilities
- Compliance frameworks (SOC 2, ISO 27001, industry-specific)
- Resource sharing flexibility (dedicated or shared based on tier)
- Enterprise-grade SLAs with tenant-specific guarantees
B2C SaaS Considerations
- High-density resource sharing for cost efficiency
- Consumer privacy regulations (GDPR, CCPA, data localization)
- Massive scale horizontal scaling for millions of users
- Simplified onboarding with social identity providers
- Usage-based billing models and freemium tiers
Common SaaS Priorities
- Scalable multitenancy with efficient resource utilization
- Rapid customer onboarding and self-service capabilities
- Global reach with regional compliance and data residency
- Continuous delivery and zero-downtime deployments
- Cost efficiency at scale through shared infrastructure optimization
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.
- 2d ago First seen · 125 lines · 34 tokens per session scan A c6cdb3e9cb60
Azure SaaS Architect mode instructions is an agent published in the GitHub repository github/awesome-copilot (38,502 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,729 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-30.
Other agents, from other repositories
documentation-writer
A specialized assistant for creating clear, comprehensive technical documentation.
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
ndv-architect
Architecture advisor. Use when designing systems, reviewing structural decisions, identifying SOLID violations, planning scalability, or when the question is whether the system is built right — not whether it works. Autistic systems thinking — needs internal consistency, sees structural violations immediately, cannot…
ndv-design
Design judgment specialist. Use when UI code, components, or flows need visual and UX assessment — or when a design decision needs principled justification. Reads code as its rendered visual output. The broken hierarchy, the absent affordance, the interaction that taxes working memory beyond its limit — these register…
ndv-forecast
Estimation realist. Use when reviewing estimates, sprint plans, roadmaps, or any commitment about time. Calibrates optimistic projections against known laws of software estimation. Temporal dysphoria as a cognitive style — viscerally aware that "almost done" is a trap, the last 10% is where time goes to die, and every…
ndv-tester
Test generation specialist. Use when writing tests, improving coverage, or ensuring correctness. Adversarial by default — assumes the code is lying, treats every untested assumption as a hidden bug, cannot accept a happy path test as proof of anything.