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 EricTechPro/startup-claude-skills --skill develop-teamgit clone --depth 1 https://github.com/EricTechPro/startup-claude-skillsWrote 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/erictechpro/startup-claude-skills/develop-team)<a href="https://agentmods.dev/skills/erictechpro/startup-claude-skills/develop-team"><img src="https://agentmods.dev/badge/skills/erictechpro/startup-claude-skills/develop-team/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/erictechpro/startup-claude-skills/develop-team"><img src="https://agentmods.dev/badge/skills/erictechpro/startup-claude-skills/develop-team.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.00074 | $0.04025 |
| Opus 5.5 | $0.00030 | $0.01610 |
| Sonnet 5.5 | $0.00015 | $0.00805 |
| Haiku 4.5 | $0.00007 | $0.00402 |
Grade A, and why
develop-team 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 — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Develop Team
Orchestrate a full feature development cycle using parallel sub-agents. Takes a ticket reference or freeform task and drives it through deep research, planning (with design/test/migration specs), implementation with per-phase test generation, review, and automatic PR creation — fully autonomous with no checkpoints unless a genuine blocker is detected.
When to Use This Skill
- Starting a new feature - Hand off a ticket and let the pipeline research, plan, and implement
- Exploring before implementing - Use
plan-only=trueto get a researched plan without writing code - Structured development - Parallel research + review instead of ad-hoc implementation
Parameters
| Parameter | Default | Description |
|---|---|---|
type |
auto |
Feature type: auto|ui-heavy|full-stack|backend-only|async-heavy |
auto-commit |
true |
Create atomic commits after each implementation phase |
skip-review |
false |
Skip refactor and review phases |
skip-tests |
false |
Skip per-phase test generation |
skip-pr |
false |
Skip automatic PR creation |
skip-migrations |
false |
Skip DB migration analysis and application |
plan-only |
false |
Stop after planning (no implementation) |
Invocation
/develop-team PROJ-123
/develop-team PROJ-123 plan-only=true
/develop-team "Add currency preferences to user settings"
/develop-team PROJ-45 auto-commit=false skip-review=true
/develop-team PROJ-67 type=ui-heavy
/develop-team PROJ-89 type=backend-only skip-tests=true skip-pr=true
Prerequisites
This skill expects the following project conventions:
- CLAUDE.md at project root — defines coding standards, patterns, folder structure, and conventions
- Ticket system (optional) — Jira MCP or similar for fetching ticket details
- Spec/backlog location — configurable; defaults to searching common locations (
/backlog/,/specs/,/docs/specs/) - Companion skills (optional) —
/refactorand/review-fixfor Phases 5-6. If not available, those phases are skipped gracefully.
What ships with it
3 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.
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 · 379 lines · 74 tokens per session scan A 3a5ceba08a1e
develop-team is a skill published in the GitHub repository EricTechPro/startup-claude-skills (60 stars, last pushed 4mo ago), licensed MIT. It adds 74 tokens to every session and 4,025 once invoked, about $0.0003 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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.