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 agentmods add skills/isvlasov/rageatc-oss/orchestrating-software-devnpx skills add isvlasov/rageatc-oss --skill orchestrating-software-devgit clone --depth 1 https://github.com/isvlasov/rageatc-ossWrote 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/isvlasov/rageatc-oss/orchestrating-software-dev)<a href="https://agentmods.dev/skills/isvlasov/rageatc-oss/orchestrating-software-dev"><img src="https://agentmods.dev/badge/skills/isvlasov/rageatc-oss/orchestrating-software-dev.svg" alt="Measured on agentmods" 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.00039 | $0.02702 |
| Opus 5 | $0.00019 | $0.01351 |
| Sonnet 5 | $0.00008 | $0.00540 |
| Haiku 4.5 | $0.00004 | $0.00270 |
Grade A, and why
orchestrating-software-dev 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 6d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrating Software Development
The orchestrator's handbook for running software projects with rageatc-code-oss: which tier to select, which agents and skills to invoke at each stage, and how to respond at every decision point. The orchestrator coordinates; agents execute. How agents do their work lives in their preloaded skills and agent definitions — never restated here.
Orchestrator-owned stages. Four stages are executed directly rather than delegated, because the artefact depends on holding the full project picture (or live dialogue with the user) that delegation would lose:
- Stage 1 — Product Definition (managing-product): dialogic requirements extraction
- Stage 4 — Interface Design (designing-interfaces): dialogic; only when the project has a UI
- Stage 6 — Enrichment (enriching-roadmap): needs PRD, architecture, and all chunk relationships simultaneously
- Stage 7 — Planning (planning-software): needs the full enriched roadmap to produce a coherent contract
If context window limits bite, session resumption via project files (ORCHESTRATION-PLAN.md, ORCHESTRATION-LOG.md) is the safety net.
Tier Selection
Select the tier before invoking any agent; it governs depth at every subsequent stage.
| Tier | Use when |
|---|---|
| Quick | Bug fix, small isolated change, 1-3 files, no new architectural decisions |
| Standard | New feature, moderate complexity — this is the default |
| Thorough | Greenfield project, cross-cutting change, complex system, multiple components |
Signals for Quick: single component, reversible, no new dependencies, scope clear without upstream work. Signals for Thorough: greenfield, new architectural territory, multiple components with shared interfaces, significant non-functional requirements, parallel workstreams. When in doubt, start Standard.
Record the selected tier and justification in the orchestration log before proceeding.
Lifecycle Stages
Stage 0 — Upstream Entry
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.
- 6d ago First seen · 217 lines · 39 tokens per session scan A dbe3ec829cab
orchestrating-software-dev is a skill published in the GitHub repository isvlasov/rageatc-oss (9 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 2,702 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-08-31.
Other skills, from other repositories
design-method
Use when starting any design task — resolves register, sets the 3 dials, locks Gate 0, and routes to the right move and target skill.
design-webapp
Use when building or extending a dashboard, SaaS screen, or any authenticated app surface — use design-web instead for a marketing site.
design-web
Use when building or revising a marketing/landing/campaign page, register brand locked at Gate 0 — use design-webapp for app screens instead.
react-tanstack-router
Use when implementing routing in a React app (NOT Next.js) with TanStack Router — file-based routes, loaders, search params.
git-flow
Use when committing, branching, opening PRs, or deciding merge/branch strategy.
fusecore
Use when creating modules, understanding FuseCore structure, or implementing features in a FuseCore modular-monolith Laravel project.