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 agent-skills-hub/agent-skills-hub --skill backend-development-feature-developmentgit clone --depth 1 https://github.com/agent-skills-hub/agent-skills-hubWrote 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/agent-skills-hub/agent-skills-hub/backend-development-feature-development)<a href="https://agentmods.dev/skills/agent-skills-hub/agent-skills-hub/backend-development-feature-development"><img src="https://agentmods.dev/badge/skills/agent-skills-hub/agent-skills-hub/backend-development-feature-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/agent-skills-hub/agent-skills-hub/backend-development-feature-development"><img src="https://agentmods.dev/badge/skills/agent-skills-hub/agent-skills-hub/backend-development-feature-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.00031 | $0.02271 |
| Opus 5.5 | $0.00012 | $0.00908 |
| Sonnet 5.5 | $0.00006 | $0.00454 |
| Haiku 4.5 | $0.00003 | $0.00227 |
Grade A, and why
backend-development-feature-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 2mo 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.
This is a copy
100% identical to backend-development-feature-development — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate end-to-end feature development from requirements to production deployment:
[Extended thinking: This workflow orchestrates specialized agents through comprehensive feature development phases - from discovery and planning through implementation, testing, and deployment. Each phase builds on previous outputs, ensuring coherent feature delivery. The workflow supports multiple development methodologies (traditional, TDD/BDD, DDD), feature complexity levels, and modern deployment strategies including feature flags, gradual rollouts, and observability-first development. Agents receive detailed context from previous phases to maintain consistency and quality throughout the development lifecycle.]
Use this skill when
- Coordinating end-to-end feature delivery across backend, frontend, and data
- Managing requirements, architecture, implementation, testing, and rollout
- Planning multi-service changes with deployment and monitoring needs
- Aligning teams on scope, risks, and success metrics
Do not use this skill when
- The task is a small, isolated backend change or bug fix
- You only need a single specialist task, not a full workflow
- There is no deployment or cross-team coordination involved
Instructions
- Confirm feature scope, success metrics, and constraints.
- Select a methodology and define phase outputs.
- Orchestrate implementation, testing, and security validation.
- Prepare rollout, monitoring, and documentation plans.
Safety
- Avoid production changes without approvals and rollback plans.
- Validate data migrations and feature flags in staging first.
Configuration Options
Development Methodology
- traditional: Sequential development with testing after implementation
- tdd: Test-Driven Development with red-green-refactor cycles
- bdd: Behavior-Driven Development with scenario-based testing
- ddd: Domain-Driven Design with bounded contexts and aggregates
Feature Complexity
- simple: Single service, minimal integration (1-2 days)
- medium: Multiple services, moderate integration (3-5 days)
- complex: Cross-domain, extensive integration (1-2 weeks)
- epic: Major architectural changes, multiple teams (2+ weeks)
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.
- 2mo ago First seen · 181 lines · 31 tokens per session scan A 7f42efa046d3
backend-development-feature-development is a skill published in the GitHub repository agent-skills-hub/agent-skills-hub (127 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 2,271 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to backend-development-feature-development, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
afrexai-api-architect
Design, build, test, document, and secure production-grade APIs. Covers the full lifecycle from schema design through deployment, monitoring, and versioning. Use when designing new APIs, reviewing existing ones, generating OpenAPI specs, building test suites, or debugging production issues.
agentmail
API-first email platform designed for AI agents. Create and manage dedicated email inboxes, send and receive emails programmatically, and handle email-based workflows with webhooks and real-time events. Use when you need to set up agent email identity, send emails from agents, handle incoming email workflows, or…
seclens-enterprise-web
Professional web application and API security testing workflows using OWASP Top 10 methodologies.
pentest-race-conditions
Concurrency exploitation — race conditions, TOCTOU vulnerabilities, and parallel request abuse in web applications.
api-designer
Design RESTful APIs with best practices for consistency and usability.
neo-rabbitmq
Use this skill when a request involves RabbitMQ message-topology design, reliability analysis, Broker operations, cluster or security configuration, monitoring, troubleshooting, or performance optimization. Use stable RabbitMQ 4.3 by default and keep development guidance language-neutral. Do not use this skill for…