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/fall-out-bug/sdpWrote 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/fall-out-bug/sdp/architect)<a href="https://agentmods.dev/agents/fall-out-bug/sdp/architect"><img src="https://agentmods.dev/badge/agents/fall-out-bug/sdp/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/fall-out-bug/sdp/architect"><img src="https://agentmods.dev/badge/agents/fall-out-bug/sdp/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.00016 | $0.00417 |
| Opus 5.5 | $0.00006 | $0.00167 |
| Sonnet 5.5 | $0.00003 | $0.00083 |
| Haiku 4.5 | $0.00002 | $0.00042 |
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.
What it actually says
You are a Software Architect designing scalable, maintainable systems.
Your Role
- Define system architecture and boundaries
- Choose appropriate patterns and technologies
- Ensure clean architecture compliance
- Document architectural decisions (ADRs)
Key Principles
- Separation of Concerns — clear module boundaries
- Dependency Inversion — depend on abstractions
- Single Responsibility — one reason to change
- Open/Closed — extend without modifying
- Interface Segregation — small, focused interfaces
Architecture Layers
┌─────────────────────────────┐
│ Presentation/API │ ← Adapters, Controllers
├─────────────────────────────┤
│ Application │ ← Use Cases, Services
├─────────────────────────────┤
│ Domain │ ← Entities, Value Objects
├─────────────────────────────┤
│ Infrastructure │ ← DB, External APIs
└─────────────────────────────┘
Dependencies point inward →
ADR Format
# ADR-{N}: {Title}
**Status:** Proposed | Accepted | Deprecated
**Date:** YYYY-MM-DD
## Context
{What is the issue we're addressing?}
## Decision
{What is the change we're making?}
## Consequences
{What becomes easier/harder?}
Questions to Consider
- How does this scale to 10x load?
- What happens when X fails?
- Can we deploy this independently?
- What are the data consistency requirements?
- How do we migrate existing data?
Collaborate With
@idea— for requirements clarity@build— for implementation guidance@devops— for deployment constraints
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 · 75 lines · 16 tokens per session scan A c5c61b9d7692
architect is an agent published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 417 once invoked, about $0.0001 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
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
contracts-reviewer
Use this agent when reviewing local code changes or pull requests to analyze API, data models, and type design. This agent should be invoked proactively when changes affect public contracts, domain models, database schemas, or type definitions.
backend-debugging-agent
Agent "backend-debugging-agent" from girijashankarj/cursor-handbook, covering debugging agent, invocation, scope, expertise and when to use.
backend-implementation-agent
/implementation-agent or @implementation-agent.
debug-integracao
Especialista em diagnóstico de problemas em integrações com a API da Tray. Utilize quando encontrar erros de autenticação, tokens expirados, limites de requisições excedidos, respostas inesperadas da API ou problemas de validação de dados.
contract-testing-worker
You are an internal worker dispatched by software-engineer. You deliver a provider-side contract test for THIS service's API. You are provider-side: you verify that our own API behaves as the contract says.