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 dhslegen/digital-delivery-team --skill backend-developmentgit clone --depth 1 https://github.com/dhslegen/digital-delivery-teamWrote 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/dhslegen/digital-delivery-team/backend-development)<a href="https://agentmods.dev/skills/dhslegen/digital-delivery-team/backend-development"><img src="https://agentmods.dev/badge/skills/dhslegen/digital-delivery-team/backend-development/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/dhslegen/digital-delivery-team/backend-development"><img src="https://agentmods.dev/badge/skills/dhslegen/digital-delivery-team/backend-development.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.00072 | $0.03104 |
| Opus 5.5 | $0.00029 | $0.01242 |
| Sonnet 5.5 | $0.00014 | $0.00621 |
| Haiku 4.5 | $0.00007 | $0.00310 |
Grade A, and why
backend-development scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl http://localhost:3001/health How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Development · 后端实现知识包
M6.4 整改:v0.6.x 用 backend-agent subagent 黑盒派发,工时不可控、用户看不到中间步骤。 v0.7.0 改 main thread + 6-phase 范式(EXPLORE→PLAN→APPROVE→IMPLEMENT→VERIFY→SUMMARY)。 本 skill 是 main thread 实现 server/ 时的"必读知识包",不再是 subagent。
Triggers
/build-api命令的 IMPLEMENT phase/impl命令串行执行后端阶段- 任何 main thread 写
server/**/*.{ts,js,java,py,go}文件时 - PR-E(v0.7.2):当
.ddt/tech-stack.json::frontend.type === "server-side"时,模板渲染(如 Thymeleaf/JSP/FreeMarker/Jinja2/...)一并由 backend 项目承载,模板路径见frontend.template_engine对应惯例(Spring Boot Thymeleaf →src/main/resources/templates/;Django →<app>/templates/;FastAPI Jinja →templates/)。/build-web此场景跳过;本 skill 必须额外覆盖模板实现。
Inputs(main thread 必读清单)
docs/api-contract.yaml(唯一接口真相源)docs/data-model.md(数据层真相源).ddt/tech-stack.json(栈选型 SSoT,禁止偏离)skills/api-contract-first/SKILL.md(契约优先原则)contexts/delivery.md(DDT 全局上下文)rules/delivery/agent-invariants.md(6 条全局不变量)rules/delivery/contract-integrity.md(契约完整性)- 当前栈对应的 TDD 范式(参考栈相关测试框架文档)
Hard Requirements(main thread 必须遵守)
- 契约 100% 匹配:每个 endpoint 的 request / response / error 必须 100% 匹配
docs/api-contract.yaml - 每个 endpoint 配集成测试:不合格不得提交(验证 happy path + 至少 1 个 edge case)
- 事务边界:数据层操作必须在
data-model.md声明的事务边界内 - migration + smoke test:跑 migration(如有 schema 变更)+ 本地 smoke test(health check + 简单 CRUD 路径)
- 日志 requestId:所有日志必须含
requestId与关键业务字段(脱敏后) - 栈刚性约束:必须使用
.ddt/tech-stack.json::backend段定义的 language / framework / build / database / orm / testing;禁止偏离 preset - SSoT 锁死:
.ddt/tech-stack.json仅可 Read,严禁 Write/Edit/MultiEdit(PreToolUse hook 会硬拦截) - validation loop:每完成一个文件立即跑 build / lint / type-check / test(按
skills/validation-loop/SKILL.md)失败立即停下决策
6-Phase 实施流程(main thread)
Phase 1: EXPLORE(理解现有代码)
如果 server/ 已有代码:
- 用
Grep/Glob/Read扫描现有结构 - 识别已有的 routing / middleware / db client / 测试套
- 找类似实现作参照(如已有 GET /tasks 实现,新增 POST /tasks 应沿用相同 pattern)
- 记录约定到
docs/build-api-exploration.md(用户可见 - 去黑盒)
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 · 223 lines · 72 tokens per session scan A b90ed3f60045
backend-development is a skill published in the GitHub repository dhslegen/digital-delivery-team (1 stars, last pushed 5mo ago), licensed MIT. It adds 72 tokens to every session and 3,104 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
cortex-integrate
Design and implement an AI feature integration — model selection, architecture pattern, system prompt, data flow, error handling, cost estimate. Use when asked to "add AI to this", "LLM integration", "add Claude/GPT", or "AI-powered feature".
spine-api
Design and spec an API — endpoints, request/response shapes, error codes, auth pattern, pagination. Applies Stripe's consistency principles. Use when asked to "design an API", "build API endpoints", "create REST API", or "API for this feature".
spine-review
API and backend code review — REST conventions, auth, validation, error handling, pagination, rate limiting, test coverage. Use when asked to "review this API", "code review", "review backend", or "pre-launch backend check".
spine-recon
Backend reconnaissance — map all routes, middleware, models, dependencies, auth, and assess code quality for project takeover. Use when asked to "understand this backend", "map the API", or "assess code quality".
knowledge-wiki
A tool that turns useful lessons from coding sessions into general articles for a team wiki. A wiki is a collection of linked reference pages, and this one can be kept locally or shared through a Git repository.
design-system-reference
Style guides and implementation rules for frontend design. Works with design-discovery agent which handles context gathering and VS-based style recommendations. Contains detailed style guides, anti-patterns, and implementation checklists.