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 skills add tranhieutt/software_development_department --skill backend-architectgit clone --depth 1 https://github.com/tranhieutt/software_development_departmentWrote 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/skills/tranhieutt/software_development_department/backend-architect)<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/backend-architect"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/backend-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/skills/tranhieutt/software_development_department/backend-architect"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/backend-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.00044 | $0.01075 |
| Opus 5 | $0.00022 | $0.00537 |
| Sonnet 5 | $0.00009 | $0.00215 |
| Haiku 4.5 | $0.00004 | $0.00108 |
Grade A, and why
backend-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 9d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Architect
Workflow
- Capture requirements: Domain context, use cases, NFRs (scale, latency, consistency)
- Define service boundaries: DDD bounded contexts, service decomposition
- Design API contracts: REST/GraphQL/gRPC with versioning strategy
- Plan communication: Sync (REST, gRPC) vs async (queues, events)
- Build in resilience: Circuit breakers, retries, timeouts, graceful degradation
- Design observability: structured logging, RED metrics, distributed tracing
- Security: Auth/Z strategy, rate limiting, secrets management
- Caching: Layer strategy (app → API → CDN) with invalidation plan
- Document: Service diagram (Mermaid), ADRs, trade-offs
API design decision matrix
| Use case | Protocol | Reason |
|---|---|---|
| Standard CRUD API | REST | Widest tooling support |
| Client queries complex data | GraphQL | Reduces over-fetching |
| Internal service-to-service | gRPC | Typed contracts, low latency |
| Real-time bidirectional | WebSocket | Full duplex |
| Server push (one-way) | SSE | Simpler than WS for unidirectional |
| High-volume async work | SQS/Kafka | Decoupling, retry, backpressure |
Service boundary rules (non-obvious)
- Bounded context = 1 database — shared DB across services creates hidden coupling; eventual consistency is the price of independence
- Sync calls create latency chains — A → B → C means P99(A) = P99(A) + P99(B) + P99(C); use async for non-blocking flows
- Saga over 2PC — distributed transactions via saga (choreography or orchestration); 2PC blocks and creates distributed deadlocks
- Stateless for horizontal scale — session state in Redis/DynamoDB, not in memory
- Database per service, not schema per service — separate schemas in shared DB = shared schema migrations = coupling still exists
Resilience patterns (always include these)
Circuit Breaker: CLOSED → [failures > threshold] → OPEN → [timeout] → HALF-OPEN → [success] → CLOSED
Retry: exponential backoff with jitter — base_delay * 2^attempt + random(0, base_delay)
Timeout: always set; propagate deadline via context/headers
Bulkhead: separate thread pools per dependency; one slow dep shouldn't starve others
Idempotency: every mutating operation needs idempotency key; store result, return on duplicate
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.
- 9d ago First seen · 97 lines · 44 tokens per session scan A 1a36c9efe737
backend-architect is a skill published in the GitHub repository tranhieutt/software_development_department (72 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 1,075 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 skills, from other repositories
architecture
Proactive architecture review — explore codebase structure, generate a self-contained HTML report with Mermaid diagrams and candidate improvements, then grill the findings. Use when planning a large refactor, onboarding to an unfamiliar codebase, or before a major architectural change.
scale-to-millions
Use this skill whenever the user is designing, reviewing, debugging, or answering interview questions about system/software architecture and scalability — e.g. "scale my app", "how do I handle more traffic", "design a URL shortener / news feed / chat system", "my API is slow under load", "should I shard my database"…
fastapi
Skill "fastapi" from DongDuong2001/pudo-code-system, covering python fastapi pudo checklist, 1. plan (architecture & strategy), 2. understand (context & auditing), 3. develop (implementation) and 4. optimize (performance & review).
backend-code
Server-side logic, data processing, and state management.
javascript-code
JavaScript/TypeScript development, paradigms, and runtime environments.
api-design-plan
Planning and designing scalable, secure, and intuitive APIs.