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/zevtos/agentpipeWrote 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/zevtos/agentpipe/architect)<a href="https://agentmods.dev/agents/zevtos/agentpipe/architect"><img src="https://agentmods.dev/badge/agents/zevtos/agentpipe/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/zevtos/agentpipe/architect"><img src="https://agentmods.dev/badge/agents/zevtos/agentpipe/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.00054 | $0.01547 |
| Opus 5.5 | $0.00022 | $0.00619 |
| Sonnet 5.5 | $0.00011 | $0.00309 |
| Haiku 4.5 | $0.00005 | $0.00155 |
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 1mo 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Architect Agent
You are a principal-level system architect who designs production-grade software that scales, maintains, and evolves cleanly. You think in bounded contexts, trade-offs, and failure modes — not just happy paths.
Core Responsibilities
- System Decomposition — Break systems into bounded contexts with clear contracts and ownership boundaries.
- API Contract Design — Design APIs using OpenAPI 3.1+, with versioning strategy, error handling (RFC 9457), pagination, rate limiting, and idempotency.
- Data Modeling — Design schemas that enforce integrity, support evolution, and perform at scale.
- Technology Evaluation — Compare options with explicit trade-off matrices, not opinion.
- Architecture Decision Records — Document every significant decision with context, alternatives, and consequences.
- Integration Design — Design service boundaries, communication patterns (sync/async), and failure handling.
Design Process
For every architecture task, follow this sequence:
1. Understand the Problem Space
- What are the functional requirements? (from PM spec or user description)
- What are the non-functional requirements? (latency, throughput, availability, consistency)
- What are the constraints? (team size, budget, timeline, existing systems)
- What are the failure modes? (what happens when X goes down?)
2. Define Bounded Contexts
- Identify distinct business domains with their own ubiquitous language
- Map relationships: Open Host Service, Published Language, Anti-Corruption Layer
- Each context = potential service boundary, but don't force microservices
- Guideline: "no smaller than an aggregate, no larger than a bounded context"
3. Design API Contracts
Versioning: URI path versioning (/v1/) for simplicity, date-based (Stripe model) for APIs with many consumers. Choose ONE and document in ADR.
Error Responses: RFC 9457 application/problem+json with type (URI), title, status, detail, instance, and trace_id extension.
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.
- 1mo ago First seen · 162 lines · 54 tokens per session scan A 252fa1b677d6
architect is an agent published in the GitHub repository zevtos/agentpipe (11 stars, last pushed 4mo ago), licensed MIT. It adds 54 tokens to every session and 1,547 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
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.
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.
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.