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 tranhieutt/software_development_department --skill team-featuregit clone --depth 1 https://github.com/tranhieutt/software_development_departmentWrote 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/tranhieutt/software_development_department/team-feature)<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/team-feature"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/team-feature/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/tranhieutt/software_development_department/team-feature"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/team-feature.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.00052 | $0.00724 |
| Opus 5 | $0.00026 | $0.00362 |
| Sonnet 5 | $0.00010 | $0.00145 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
team-feature 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 8d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When this skill is invoked, orchestrate the feature team through a structured delivery pipeline.
Decision Points: At each phase transition, use AskUserQuestion to present
the user with the subagent's proposals as selectable options. Write the agent's
full analysis in conversation, then capture the decision with concise labels.
The user must approve before moving to the next phase.
Team Composition
- product-manager — Feature scope, user stories, acceptance criteria
- ux-designer — User flows, wireframes, interaction design
- backend-developer — API design and implementation
- frontend-developer — UI components and client-side integration
- qa-engineer — Test planning and validation
How to Delegate
Use the Task tool to spawn each team member as a subagent:
subagent_type: product-managersubagent_type: ux-designersubagent_type: backend-developersubagent_type: frontend-developersubagent_type: qa-engineer
Always provide full context in each agent's prompt (feature requirements, existing patterns, API conventions). Launch independent agents in parallel where the pipeline allows (e.g., backend + UX design can proceed in parallel after spec is approved).
Pipeline
Phase 1: Feature Specification
Delegate to product-manager:
- Write the user story and acceptance criteria
- Define out-of-scope explicitly
- Identify success metrics
- Output: PRD or user story with acceptance criteria
Phase 2: Design (parallel)
Launch in parallel:
- ux-designer: User flow, wireframes, interaction spec for the feature
- backend-developer: API contract design (endpoints, request/response schemas)
Both must complete before Phase 3.
Phase 3: Review Designs
Use AskUserQuestion to get approval on:
- UX flow and wireframes
- API contract
Iterate until approved.
Phase 4: Implementation (parallel where possible)
- backend-developer: Implement approved API endpoints and business logic
- frontend-developer: Implement UI components (can start with mock data if backend not ready)
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.
- 8d ago First seen · 80 lines · 52 tokens per session scan A 9cdbbd9674e0
team-feature is a skill published in the GitHub repository tranhieutt/software_development_department (72 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 724 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
triage
Apply a formal state machine to issues — assign category (bug/enhancement/question/spike) and state (needs-triage → needs-info → ready-for-agent → ready-for-human → wontfix). Issues marked ready-for-agent become inputs to supergraph:plan. Use when processing a backlog, reviewing new issues, or preparing work for…
task-code
A two-phase workflow for breaking coding work into tracked subtasks and progress records. It applies rules from the project's CLAUDE.md file, which is a set of instructions for the coding assistant.
cm-sprint-bus
Use to run the full sprint pipeline: brainstorm → plan → design → tdd → build → review → qa → security → ship → monitor → retro.
adopt
Take a folder that already holds research — papers, notes, code, half-written drafts — into MAGI, without breaking what is already there.
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
estimating-and-contingency
Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one…