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 Data-Wise/craft --skill backend-designergit clone --depth 1 https://github.com/Data-Wise/craftWrote 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/data-wise/craft/backend-designer)<a href="https://agentmods.dev/skills/data-wise/craft/backend-designer"><img src="https://agentmods.dev/badge/skills/data-wise/craft/backend-designer/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/data-wise/craft/backend-designer"><img src="https://agentmods.dev/badge/skills/data-wise/craft/backend-designer.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.00053 | $0.00784 |
| Opus 5.5 | $0.00021 | $0.00314 |
| Sonnet 5.5 | $0.00011 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
backend-designer 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Designer Skill
Auto-activated when: User discusses backend architecture, API design, database decisions, or authentication patterns.
Core Capabilities
1. API Design Patterns
- RESTful API structure (resources, endpoints, versioning)
- GraphQL schema design
- API authentication (JWT, OAuth, API keys)
- Rate limiting and throttling strategies
- Error handling and status codes
2. Database Design
- Schema design (normalized vs denormalized)
- Index strategies for performance
- Migration planning
- ORM vs raw SQL trade-offs
- Connection pooling
3. Authentication & Authorization
- Session management (JWT vs session cookies)
- OAuth flows (authorization code, client credentials)
- Permission models (RBAC, ABAC)
- Secure token storage
- Password hashing (bcrypt, argon2)
4. Performance Patterns
- Caching strategies (Redis, in-memory, CDN)
- Query optimization
- Background jobs (Celery, Bull, Temporal)
- Horizontal scaling considerations
- Database read replicas
Design Philosophy: Solid Indie
Ship Fast Principles:
- Start with monolith, extract services only when needed
- Use proven patterns, avoid trendy frameworks
- Prefer boring technology that works
- Document trade-offs, not just decisions
Anti-Patterns to Avoid:
- ❌ Microservices for < 5 person teams
- ❌ Over-abstraction (generic repositories, factories)
- ❌ Premature optimization
- ❌ Complex caching before measuring
Delegation Strategy
When analysis is needed, I will:
- Analyze current state - Review existing code/architecture
- Delegate to agents when feasible:
backend-architectagent for deep architectural analysisdatabase-architectagent for schema optimizationsecurity-specialistagent for auth review
- Run in background - Use Task tool with
run_in_background: true - Synthesize results - Combine agent outputs into actionable recommendations
Example Activation
User: "I need to design an API for user authentication with social login"
Skill activates and provides:
1. Quick assessment of requirements
2. Recommends OAuth 2.0 flow (authorization code + PKCE)
3. Suggests passport.js or similar proven library
4. Outlines token storage strategy
5. Delegates security review to security-specialist agent (background)
6. Returns with comprehensive auth implementation plan
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 · 118 lines · 53 tokens per session scan A ff1fbf380600
backend-designer is a skill published in the GitHub repository Data-Wise/craft (4 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 784 once invoked, about $0.0002 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
database-patterns
Database design and migration patterns for Alembic migrations, schema design (SQL/NoSQL), and database versioning. Use when creating migrations, designing schemas, normalizing data, managing database versions, or handling schema drift.
neo4j-getting-started-skill
Orchestrates zero-to-running-app in 8 stages — prerequisites → context → provision → model → load → explore → query → build. Each stage reads its own reference file. Supports HITL and fully autonomous operation. Use when starting a new Neo4j project from scratch, provisioning Aura, generating synthetic data, building…
neo4j-graphql-skill
Build and configure a GraphQL API backed by Neo4j using @neo4j/graphql v7 (current) or v5 (LTS). Covers Neo4jGraphQL constructor, getSchema(), assertIndexesAndConstraints(), type definitions with @node, @relationship (IN/OUT/UNDIRECTED), @cypher for custom resolvers, @authorization/@authentication for JWT/JWKS…
neo4j-kafka-skill
Configure and operate the Neo4j Connector for Kafka (sink + source) and the native Neo4j CDC API. Covers Cypher/Pattern/CUD sink strategies, CDC-based and query-based source, exactly-once semantics, DLQ error handling, Confluent Cloud managed connector, schema registry (Avro/JSON), and native db.cdc.query cursor-loop…
architecture-paradigm-cqrs-es
Applies CQRS and Event Sourcing for read/write separation and audit trails. Use when designing systems with complex domain logic or full state-change history.
backend-cqrs-patterns
Use this skill when the user says 'CQRS', 'command query segregation', 'separate read write model', 'command model', 'query model', 'read model', 'write model', 'materialized view', 'command handler', 'query handler'. This skill enforces: strict command/query separation, write model optimized for consistency, read…