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 qte77/claude-code-plugins --skill designing-backendgit clone --depth 1 https://github.com/qte77/claude-code-pluginsWrote 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/qte77/claude-code-plugins/designing-backend)<a href="https://agentmods.dev/skills/qte77/claude-code-plugins/designing-backend"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/designing-backend/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/qte77/claude-code-plugins/designing-backend"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/designing-backend.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.00037 | $0.00382 |
| Opus 5.5 | $0.00015 | $0.00153 |
| Sonnet 5.5 | $0.00007 | $0.00076 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
designing-backend 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 17d 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
Backend Architecture
Git Context
- Recent changes: !
git log --oneline -3 - Current branch: !
git branch --show-current
Target: $ARGUMENTS
Creates focused, streamlined backend system designs matching stated requirements exactly. No over-engineering.
Workflow
- Read backend requirements from specified documents
- Validate scope - Simple data processing vs Complex system architecture
- Design minimal solution matching stated complexity
- Create focused deliverables - single doc for simple, multiple for complex
- Use make recipes for all commands
Architecture Strategy
Simple Processing: Basic functions, lightweight integration, existing patterns Complex Systems: Multi-tiered pipelines, PydanticAI orchestration, async patterns Performance targets: <1s simple operations, scalable for complex systems
Output Standards
Simple Tasks: Single focused backend specification Complex Tasks: Multiple targeted architecture files All outputs: Concise, streamlined, no unnecessary complexity
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.
- 17d ago Changed 74c9a307d921
- 1mo ago First seen · 46 lines · 37 tokens per session scan A 8b1803f00207
designing-backend is a skill published in the GitHub repository qte77/claude-code-plugins (3 stars, last pushed 4d ago), licensed Apache-2.0. It adds 37 tokens to every session and 382 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-31.
Other skills, from other repositories
design-code-architecture
Guided journey from an app idea to a deliberate architecture: boundaries, domain model, data decisions, and resilience, making only the expensive-to-reverse decisions and deferring the rest. Orchestrates eight skills phase by phase - clean-architecture, domain-driven-design, system-design, ddia-systems…
system-design
Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "design Twitter", "design Uber", "design a news feed", "system…
go-structure
Recommend and scaffold Go project layouts by type (CLI, API, library, monorepo). Use when starting a Go project, when asked about package organization, or when reviewing structure for anti-patterns (utils packages, over-nesting, misused pkg/).
lark-openapi-explorer
A skill for finding and calling Lark APIs that are not already available through existing commands. An API is a defined way for software to request work from another service.
lark-skill-maker
A guide for creating reusable coding-agent skills that call Feishu APIs through lark-cli. lark-cli is a command-line tool for accessing Feishu operations from a terminal.
scaffold-fastapi-vite-saas
A starter project for a self-hosted web app with a FastAPI Python backend and a Vite single-page frontend in one Git repository. A monorepo is one repository that holds multiple parts of a project.