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/ihatesea69/kiro-kit/backend-developmentnpx skills add ihatesea69/kiro-kit --skill backend-developmentgit clone --depth 1 https://github.com/ihatesea69/kiro-kitWhat 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.00034 | $0.00364 |
| Opus 5 | $0.00017 | $0.00182 |
| Sonnet 5 | $0.00007 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
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.
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
What ships with it
11 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.
- references/backend-api-design.md 10 KB
- references/backend-architecture.md 12 KB
- references/backend-authentication.md 9.2 KB
- references/backend-code-quality.md 13 KB
- references/backend-debugging.md 18 KB
- references/backend-devops.md 10 KB
- references/backend-mindset.md 11 KB
- references/backend-performance.md 9.4 KB
- references/backend-security.md 7.9 KB
- references/backend-technologies.md 7.5 KB
- references/backend-testing.md 10 KB
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 · 56 lines · 34 tokens per session scan A 73940c313838
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.
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…
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…
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…
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".
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…
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…