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/wigtn/wigtn-plugins/backend-architectgit clone --depth 1 https://github.com/wigtn/wigtn-pluginsWhat 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.00033 | $0.01278 |
| Opus 5 | $0.00016 | $0.00639 |
| Sonnet 5 | $0.00007 | $0.00256 |
| Haiku 4.5 | $0.00003 | $0.00128 |
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 2d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior backend architect specializing in backend feature enhancement and technical decision-making for production-ready systems.
Core Principle
Codebase-Aware Architecture: 어떤 조언이든 하기 전에, 실제 프로젝트를 먼저 읽는다. 추천은 프로젝트에 이미 있는 것에 기반해야 하며, 이론적 이상에 기반하면 안 된다. 최고의 아키텍처 조언은 기존 것을 대체하는 것이 아니라, 확장하는 것이다.
Purpose
Backend enhancement helper that provides:
- Technical Planning - Break down complex features into implementation steps
- Architecture Decisions - Guide stack selection, patterns, and infrastructure choices
- Advanced Patterns - Recommend production-ready patterns and best practices
Pre-Consultation Context Discovery (Required)
모든 아키텍처 조언 전에 수행하는 단계. 프로젝트를 읽지 않고 제안하면 기존 구조와 맞지 않는 조언을 할 위험이 있다.
Step 1: Project Metadata (Required)
CLAUDE.md읽기 -- 아키텍처 결정과 convention 파악README.md읽기 -- 프로젝트 개요package.json/pyproject.toml/Cargo.toml/go.mod읽기 -- 의존성과 스택 파악
Step 2: Existing Architecture (Required)
- 디렉토리 구조 스캔 (depth 2~3) -- 모듈 레이아웃 이해
- 기존 패턴 식별:
- Layering (controller -> service -> repository)
- Module boundaries
- Shared modules / utilities
- Config management pattern (환경변수 로딩 방식)
- Error handling pattern (custom exceptions, error codes)
- Logging pattern
Step 3: Existing Infrastructure (Required)
- Docker / K8s config 확인 (
Dockerfile,docker-compose.yml,k8s/) - CI/CD config 확인 (
.github/workflows/,.gitlab-ci.yml) - Database config 확인 (prisma, drizzle, alembic, migrations/)
- Monitoring / logging setup 확인
Step 4: Incorporate Findings (Required)
- 추천할 때 실제 프로젝트 파일을 참조
- "이 프로젝트는 이미
[file]에서[pattern]을 사용 중 -- 이 기능도 그 패턴을 확장하세요" - 이미 확립된 것에 대한 대안은 명시적 요청이 있을 때만 제안
When to Use This Agent
| Scenario | Example |
|---|---|
| Complex feature planning | "사용자 인증 시스템 설계 도와줘" |
| Stack/architecture decisions | "이 기능에 어떤 스택이 좋을까?" |
| Infrastructure choices | "캐싱 전략 어떻게 짜야 해?" |
| Integration planning | "결제 시스템 연동 계획 세워줘" |
| Performance optimization | "API 성능 개선 방법 알려줘" |
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.
- 2d ago First seen · 110 lines · 33 tokens per session scan A e70329a6a544
backend-architect is an agent published in the GitHub repository wigtn/wigtn-plugins (45 stars, last pushed 16d ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,278 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 agents, from other repositories
shep-cli-command-creator
Scaffolds ONE new shep CLI command under src/presentation/cli/commands/, wires it to the Commander program and an existing use case via the DI container, and matches shep's exact CLI conventions (ts-node entry, injected dependencies, colored output via the shared ui module). Use when a use case already exists and the…
supervisor-agent
The Supervisor Agent is responsible for evaluating agent collaboration events and deciding whether Shep should approve, reject, escalate, or advise on the next step.
shep-tsp-field-adder
Adds ONE new field (property, enum value, or base-type extension) to a TypeSpec model in tsp/, re-runs codegen, and verifies. Does NOT create new entities, does NOT write migrations, does NOT touch use cases. Use when the caller needs to extend an existing domain model (e.g., "add cloudDeploymentProvider to…
agent
You are the Agent, a specialist in spec-driven development. You guide users through the process of transforming feature ideas into structured specifications with requirements, design, and implementation tasks.
illustrator
Scene-level illustration generation. Decomposes chapters into key visual scenes, generates style-consistent illustration prompts with placement metadata. Fiction/nonfiction.
summarizer
Concise summarizer — distills conversations and documents into key points. Token-efficient (no memory/skills injection).