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 skills/drag88/claude-dev-framework/backend-patternsnpx skills add drag88/claude-dev-framework --skill backend-patternsgit clone --depth 1 https://github.com/drag88/claude-dev-frameworkWhat 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.00025 | $0.00827 |
| Opus 5 | $0.00013 | $0.00413 |
| Sonnet 5 | $0.00005 | $0.00165 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
backend-patterns 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 yesterday.
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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Patterns Skill
Provide guidance on backend architecture patterns, API design, and server-side best practices.
When to Activate
- During backend implementation tasks
- When designing APIs or services
- When working with databases and data layers
- When implementing authentication, authorization, or security features
Pattern Index
API Design
| Pattern | When to Use |
|---|---|
| RESTful conventions | Standard CRUD operations on resources |
| Response format | Consistent success/error JSON structure |
| Pagination | List endpoints returning multiple items |
See
references/api-design.mdfor REST conventions table, response formats, and pagination implementation.
Service Architecture
| Pattern | When to Use |
|---|---|
| Repository | Separate data access from business logic |
| Service Layer | Encapsulate business logic, coordinate side effects |
See
references/service-patterns.mdfor repository interface and service layer implementations.
Authentication & Authorization
| Pattern | When to Use |
|---|---|
| Auth middleware | Protecting routes with Bearer token verification |
| Authorization middleware | Role-based route protection |
| JWT tokens | Access + refresh token generation and rotation |
| RBAC | Permission checks with wildcard and ownership support |
See
references/auth-middleware.mdfor middleware, JWT, and RBAC implementations.
Database
| Pattern | When to Use |
|---|---|
| N+1 prevention | Loading related data (eager load or batch) |
| Transactions | Multi-step operations requiring atomicity |
| Caching (decorator) | Frequently read, rarely written data |
See
references/database-patterns.mdfor N+1 fixes, transaction pattern, and cache-aside implementation.
Error Handling
| Pattern | When to Use |
|---|---|
| Error class hierarchy | Typed errors with status codes (NotFound, Validation, etc.) |
| Error middleware | Global Express error handler |
| Retry with backoff | Transient failures (network, rate limits) |
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 109 lines · 25 tokens per session scan A d9238c5ad364
backend-patterns is a skill published in the GitHub repository drag88/claude-dev-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 827 once invoked, about $0.0001 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…