backend-development

Guidance for building backend software with Node.js, Python, or Go. Backend software runs on servers and commonly handles APIs, databases, authentication, background jobs, and integrations.

In plain words
What is it for?
Use it when implementing APIs, middleware, services, database integrations, queues, or other server-side systems.
Why use it?
It provides a consistent approach to validation, architecture, errors, logging, configuration, health checks, and safe shutdowns.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/ihatesea69/kiro-kit/backend-development
Any agent
npx skills add ihatesea69/kiro-kit --skill backend-development
Clone the repo
git clone --depth 1 https://github.com/ihatesea69/kiro-kit

Made for: Claude Code, Codex.

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 364 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00034 $0.00364
Opus 5 $0.00017 $0.00182
Sonnet 5 $0.00007 $0.00073
Haiku 4.5 $0.00003 $0.00036

Measured 2d ago against content hash 73940c313838, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

backend-development 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.

.kiro/skills/backend-development/SKILL.md · 56 lines

What it actually says

Backend Development

Activate this skill when building backend services, APIs, or server-side logic.

When to Use

  • Implementing REST or GraphQL API endpoints
  • Building middleware (auth, logging, rate limiting, CORS)
  • Designing service layer architecture
  • Integrating with databases and external services
  • Implementing background jobs and queues
  • Setting up application configuration and environment management

Architecture Patterns

  • Layered: Controller -> Service -> Repository
  • Clean Architecture: separate domain from infrastructure
  • CQRS: separate read and write models for complex domains
  • Event-driven: pub/sub for decoupled services

Implementation Guidelines

  • Validate all input at the boundary (controller/handler layer)
  • Use dependency injection for testability
  • Implement structured logging with correlation IDs
  • Handle errors at appropriate layers (do not swallow exceptions)
  • Use environment variables for configuration (12-factor app)
  • Implement health check endpoints (/health, /ready)
  • Use connection pooling for database connections
  • Implement graceful shutdown handling

Error Handling

  • Use typed error classes with error codes
  • Return consistent error response format
  • Log errors with context (request ID, user ID, operation)
  • Never expose internal details in production error responses
  • Implement global error handler as safety net

Testing Strategy

  • Unit tests for service/business logic (no I/O)
  • Integration tests for database and external service interactions
  • API tests for endpoint behavior verification
  • Load tests for performance-critical paths
Changes

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.

  1. 2d ago First seen · 56 lines · 34 tokens per session scan A 73940c313838

Subscribe to this mod's changes

backend-development is a skill published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 13d ago), licensed MIT. It adds 34 tokens to every session and 364 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.

Related

Other skills, from other repositories

computer-use

Read and drive native desktop applications through the accessibility layer — list on-screen apps, snapshot one window as a numbered element tree, then click / type / set a value / scroll / drag / run a named action, by element index or by screen coordinates. Use for work in a desktop app rather than a web page. Full…

kirodotdev/KiroCrew · 105 tokens

writing-tests

How to write a Kiro Crew backend test that has NO side effects and does not flake. Use when adding, editing, reviewing, or debugging a pytest test in the Kiro Crew source repo: which conftest is under your file, what leaks (temp dirs, the real data home, /.kiro, cron, threads, child processes), how to tell which of…

kirodotdev/KiroCrew · 123 tokens

five-whys

Enter a guided dive-deep research mode — 5 Whys is the default engine (one focused question at a time along a What-it-is -> Example -> Why-not-alternatives -> Benefits -> Costs chain, user-steered branching), every step appended to an event-sourced log the tree and report are folded from, and extensible with plug-in…

kirodotdev/KiroCrew · 88 tokens

artifact-deploy

One-click deploy a user's pre-built app/artifact into their OWN AWS account and get a global public HTTPS link (Vercel-like), with a default TTL and promote-to-persistent. Use when the user says "deploy this", "ship this demo", "give me a public link", "share this externally", or "deploy to AWS".

kirodotdev/KiroCrew · 74 tokens

self-nudge-loop

Build a reactive same-session autonomy loop using KiroCrew's AutoNudgeService. One long-lived dashboard session keeps working toward a goal — when its turn completes and no user input arrives within idlesecs, the service auto-injects a nudge message into the SAME session. Survives tab close, logout, and gateway…

kirodotdev/KiroCrew · 131 tokens

pipeline-conductor

Operating procedure for the kirocrew-pipeline-conductor agent - run one issue/PR pipeline on one repository as a supervised fleet. Auto-pick items, stand up one worker session per item in a dedicated folder, probe them each cycle with one script call, verify claimed greens independently, intervene when a worker loops…

kirodotdev/KiroCrew · 121 tokens