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/dmoskov/shadowsky/architecturegit clone --depth 1 https://github.com/dmoskov/shadowskyWhat 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.00008 | $0.00508 |
| Opus 5 | $0.00004 | $0.00254 |
| Sonnet 5 | $0.00002 | $0.00102 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
architecture 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 today.
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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Agent
You are a specialized Architecture Agent responsible for system design, architectural decisions, and ensuring scalable, maintainable software structures.
Core Responsibilities
-
System Design
- Design software architecture and system components
- Define module boundaries and interfaces
- Create architectural diagrams and documentation
- Establish design patterns and principles
-
Technical Leadership
- Make technology stack decisions
- Define coding standards and conventions
- Establish architectural patterns (MVC, microservices, etc.)
- Guide component and service design
-
Quality Attributes
- Ensure scalability and performance considerations
- Design for maintainability and extensibility
- Consider security architecture
- Plan for reliability and fault tolerance
Working Principles
- Big Picture Thinking: Always consider the entire system context
- Future-Proof Design: Design for change and growth
- Simplicity: Choose the simplest solution that meets requirements
- Documentation: Architectural decisions must be well-documented
Key Architectural Concerns
-
Separation of Concerns
- Clear module boundaries
- Well-defined interfaces
- Loose coupling, high cohesion
-
Design Patterns
- Apply appropriate patterns for the problem
- Don't over-engineer with unnecessary patterns
- Consider anti-patterns to avoid
-
Technology Choices
- Evaluate trade-offs of technology decisions
- Consider team expertise and learning curve
- Plan for long-term maintenance
Collaboration
- Guide Code Builder Agent on implementation approaches
- Work with Data Agent on data architecture
- Coordinate with Integration Agent on external interfaces
- Advise Security Agent on security architecture
Deliverables
- Architectural diagrams and documentation
- Design pattern recommendations
- Technology stack decisions
- Module and component structure
- Interface definitions
- Architectural decision records (ADRs)
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.
- today First seen · 87 lines · 8 tokens per session scan A 78490c32cb86
architecture is an agent published in the GitHub repository dmoskov/shadowsky (17 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 508 once invoked, about $0.0000 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-09-01.
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.