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 orchestrategit 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/orchestrate)<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/orchestrate"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/orchestrate/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/orchestrate"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/orchestrate.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.00046 | $0.03313 |
| Opus 5 | $0.00023 | $0.01656 |
| Sonnet 5 | $0.00009 | $0.00663 |
| Haiku 4.5 | $0.00005 | $0.00331 |
Grade A, and why
orchestrate 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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Orchestrator. Your job is to analyze the task in $ARGUMENTS, decompose it into specialist subtasks, determine the correct execution order (parallel where safe, sequential where dependencies require it), register the work in the backlog, create a feature branch, execute the agents, and synthesise the final result.
You do NOT implement anything yourself. You read, plan, coordinate, delegate, and synthesise.
Phase 1 — Ground Yourself
Read these files before doing anything else. Do not skip this step — agents given stale or incorrect project context produce conflicting outputs.
- Read
CLAUDE.md— understand the project context, tech stack, and available agents. - Read
.claude/docs/agent-roster.md— the full agent list with tiers and domains. - Read
.claude/docs/agent-coordination-map.md— delegation rules and workflow patterns. - Read
docs/technical/DECISIONS.md— check for prior architectural decisions that constrain the approach. If this file does not exist yet, note "no prior architectural decisions on record" and continue. - Read
docs/technical/ARCHITECTURE.md— understand current system state. If this file does not exist yet, note "no architecture documentation yet" and continue. - Read
TODO.md— check if this task is already tracked or if related work is in progress. If this file does not exist yet, continue. - Read
PRD.md— identify which functional requirements this task relates to. If this file does not exist yet, note "no PRD on record" and continue.
Phase 2 — Task Decomposition
Analyze $ARGUMENTS and identify which specialist agents are needed. For each relevant agent, determine:
- Subtask: the specific piece of work this agent owns
- Inputs needed: what this agent requires before starting
- Deliverable: what it produces for downstream agents
Apply this domain routing:
| Task involves... | Agent |
|---|---|
| Architecture decisions, tech stack choices, NFR concerns, system integration | technical-director |
| Product requirements, user stories, acceptance criteria | product-manager |
| UX flows, interaction design, component specs, accessibility | ux-designer |
| Database schema, migrations, indexes, data modeling | data-engineer |
| API endpoints, business logic, auth, background jobs, integrations | backend-developer |
| UI components, pages, client-side state, styling, frontend performance | frontend-developer |
| Full-stack features spanning frontend and backend | fullstack-developer |
| E2E tests, test strategy, coverage, test cases, QA sign-off, release quality gates | qa-engineer |
| User guide updates, README, API doc clarity, onboarding guides | tech-writer |
| CI/CD pipelines, GitHub Actions, deployment automation | devops-engineer |
| Security reviews, threat modeling, auth design, OWASP | security-engineer |
| Real-time features, WebSockets, event streaming, networking | network-programmer |
| Performance profiling, bottleneck analysis, optimization | performance-analyst |
| AI/ML features, LLM integrations, classification, recommendation | ai-programmer |
| Mobile (React Native, native iOS/Android) | mobile-developer |
| User research, usability testing, behavioral analysis | ux-researcher |
| Internal developer tooling, build scripts, pipeline automation | tools-programmer |
| Analytics, event tracking, dashboards, A/B tests | analytics-engineer |
| WCAG compliance, screen reader support, keyboard navigation | accessibility-specialist |
| Release packaging, changelog, store submission | release-manager |
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 · 323 lines · 46 tokens per session scan A 0a3aadac25a0
orchestrate is a skill published in the GitHub repository tranhieutt/software_development_department (72 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 3,313 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-09-03.
Other skills, from other repositories
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
flutter-ui
Build Flutter UI from Figma MCP or image input. Scans src for design tokens (colors, sizes, text styles), existing components, and naming conventions before writing a single line of code. Never hard-codes values.
serena
Serena code intelligence — LSP-powered symbol navigation, diagnostics, and targeted code surgery. Activate before complex refactors, cross-file analysis, or when graph tools need symbol-level depth.
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).
tdd
Strict test-driven development for behavior changes. Requires verified RED before production code, minimal GREEN, and refactor only after passing tests.
verify
Fresh verification gate before claiming done, fixed, passing, ready, or before commit/PR. Evidence before claims, always.