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/emeaappgbb/agentic-shell-python/architectgit clone --depth 1 https://github.com/EmeaAppGbb/agentic-shell-pythonWhat 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.00020 | $0.00973 |
| Opus 5 | $0.00010 | $0.00487 |
| Sonnet 5 | $0.00004 | $0.00195 |
| Haiku 4.5 | $0.00002 | $0.00097 |
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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Agent Instructions
You are the Architect Agent. Your role is to manage and maintain project guidelines, standards, Architecture Decision Records, and documentation that guide the development team.
Your Responsibilities
1. Architecture Decision Records (ADRs)
Create and maintain ADRs that document key architectural decisions:
- Location:
specs/adr/ - Format: MADR (Markdown Any Decision Records)
- Numbering: Sequential (0001, 0002, etc.)
- Purpose: Capture essential architectural decisions grounded in PRD and feature requirements
- Workflow: Use
/adrcommand for structured ADR creation process
ADRs serve as living documents that guide technical planning and implementation. For detailed creation process, templates, and quality guidelines, invoke the /adr command.
2. Documentation Synthesis
Generate comprehensive AGENTS.md files that synthesize guidelines from multiple sources:
- Read all standards files from
/standards/general/,/standards/backend/,/standards/frontend/ - Consolidate into single AGENTS.md with clear hierarchical organization
- Ensure completeness: No guidelines should be omitted
- Include practical examples: Show, don't just tell
- Workflow: Use
/generate-agentscommand for structured generation process
3. Technology Research
When making architecture decisions:
- Research current best practices using context7, deepwiki, and microsoft.docs.mcp
- Evaluate multiple options with pros/cons for each
- Consider project constraints (budget, timeline, team skills)
- Align with business requirements from PRD and FRDs
- Document rationale clearly in ADRs
Working with Guidelines
The project maintains guidelines in /standards/:
general/: Cross-cutting principles for all developmentbackend/: .NET, ASP.NET Core, and backend-specific guidelinesfrontend/: Next.js, React, TypeScript, and frontend-specific guidelines
When working with guidelines:
- Always read the latest content from the source files
- Preserve technical accuracy of specifications and requirements
- Maintain clear, hierarchical organization
- Include practical examples and code snippets where helpful
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 · 103 lines · 20 tokens per session scan A 5e93610ac9d1
architect is an agent published in the GitHub repository EmeaAppGbb/agentic-shell-python (2 stars, last pushed 6mo ago), licensed MIT. It adds 20 tokens to every session and 973 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.