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 Luohaothu/everything-codex --skill orchestrategit clone --depth 1 https://github.com/Luohaothu/everything-codexWrote 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/luohaothu/everything-codex/orchestrate)<a href="https://agentmods.dev/skills/luohaothu/everything-codex/orchestrate"><img src="https://agentmods.dev/badge/skills/luohaothu/everything-codex/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/luohaothu/everything-codex/orchestrate"><img src="https://agentmods.dev/badge/skills/luohaothu/everything-codex/orchestrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00034 | $0.00464 |
| Opus 5.5 | $0.00014 | $0.00186 |
| Sonnet 5.5 | $0.00007 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00046 |
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 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.
What it actually says
Full Feature Workflow
Orchestrate a complete feature implementation through sequential skill invocations.
Usage
/orchestrate feature <description> # Full feature workflow
/orchestrate bugfix <description> # Bug fix workflow
/orchestrate refactor <description> # Refactoring workflow
/orchestrate security <description> # Security-focused review
Workflow Types
Feature
/plan → /tdd → /code-review → /security-review
Bugfix
(investigate) → /tdd → /code-review
Refactor
/plan → /code-review → /tdd
Security
/security-review → /code-review → /plan
Workflow Phases
Phase 1: Planning
Use /plan to analyze requirements and create implementation plan.
Wait for user confirmation before proceeding.
Phase 2: Test-Driven Development
Use /tdd to write tests first, then implement.
Follow RED → GREEN → REFACTOR cycle.
Phase 3: Code Review
Use /code-review to review code quality.
Address CRITICAL and HIGH issues before continuing.
Phase 4: Security Review
Use /security-review for security audit.
Fix any CRITICAL security issues.
Between Phases
After each phase, provide:
- Summary of what was accomplished
- Any issues found and how they were resolved
- Handoff context for the next phase
Handoff Document
## HANDOFF: [previous-phase] → [next-phase]
### Context
Summary of what was done
### Findings
Key discoveries or decisions
### Files Modified
List of files touched
### Open Questions
Unresolved items for next phase
Tips
- Start with planning for complex features
- Always include code review before merge
- Use security review for auth/payment/PII
- Keep handoffs concise
- Run verification between phases if needed
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 · 95 lines · 34 tokens per session scan A 0440e48cda66
orchestrate is a skill published in the GitHub repository Luohaothu/everything-codex (25 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 464 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…