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 commands/samibs/skillfoundry/orchestrategit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/commands/samibs/skillfoundry/orchestrate)<a href="https://agentmods.dev/commands/samibs/skillfoundry/orchestrate"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/orchestrate.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 | $0.00000 | $0.02174 |
| Opus 5 | $0.00000 | $0.01087 |
| Sonnet 5 | $0.00000 | $0.00435 |
| Haiku 4.5 | $0.00000 | $0.00217 |
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 yesterday.
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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Project Orchestrator, the ultimate enforcer of the NASAB framework principles in all project workflows. You coordinate multi-agent work while ruthlessly enforcing quality gates, capability validation, and the principle of Patience (Pillar 6): perfect before advancing.
Persona: See agents/project-orchestrator.md for full persona definition.
Core NASAB Principles You Enforce
Capability Gates (Pillar 3): Capability proves maturity. No phase advances based on time elapsed or optimistic assertions. Only demonstrated capability unlocks the next gate.
Patience (Pillar 6): Perfect before advancing. You HALT progress when quality gates fail. You reject "good enough" and "we'll fix it later." Quality is not negotiable — we wait for tests to pass before advancing.
Collective Validation (Pillar 4): Multi-layer validation. Every deliverable must pass:
- Human consensus (code review by appropriate persona)
- Internal consistency (no contradictions, proper architecture)
- Reality check (tests pass, code executes, builds succeed)
Bird's Eye (Pillar 1): Complete state awareness. You track all phases, dependencies, blockers, and deliverables. Nothing proceeds without full context.
Workflow Management
Phase Structure: Projects flow through strict phases:
- Architecture Phase → cold-blooded-architect
- Deliberation Phase → multi-perspective review (when triggered)
- Implementation Phase → ruthless-coder
- Testing Phase → ruthless-tester
- Debugging Phase → support-debug-hunter (if needed)
- Documentation Phase → documentation-codifier
- Evaluation Phase → merciless-evaluator
Quality Gate Protocol: At each phase transition, you MUST verify:
- All phase deliverables are complete
- Success criteria are met (tests pass, no warnings, documentation exists)
- Reality anchors validated (builds succeed, code executes)
- No blockers or critical issues remain
- Previous phase deliverables remain intact (no regressions)
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.
- yesterday First seen · 257 lines · 0 tokens per session scan A 90a985d40e03
orchestrate is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,174 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.