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/markshust/hcf/plan-orchestratenpx skills add markshust/hcf --skill plan-orchestrategit clone --depth 1 https://github.com/markshust/hcfWhat 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.00072 | $0.05583 |
| Opus 5 | $0.00036 | $0.02792 |
| Sonnet 5 | $0.00014 | $0.01117 |
| Haiku 4.5 | $0.00007 | $0.00558 |
Grade A, and why
plan-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 2d 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 — 564 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Orchestrate
Execute all tasks in a plan using parallel TDD workers. Fully autonomous after invocation.
Usage
plan-orchestrate {plan-name}
Example: plan-orchestrate user-auth
Prerequisites
First, resolve the plans directory, once, and reuse $PLANS_DIR for every path below. It is .claude/plans unless the project overrides it in .claude/hcf.json (see Plans Directory in the README). The script answers with an absolute path resolved from the project root, so the result does not depend on the working directory:
PLANS_DIR="$("{skill-base-dir}/../../hooks/resolve-plans-dir.sh")" || exit 1
Never substitute a hand-written jq line or a literal .claude/plans. A non-zero exit means the project root or the configured value is unusable; surface the script's stderr verbatim and stop. Quote every path built from $PLANS_DIR — a configured directory may contain spaces.
Then:
- Plan must exist at
$PLANS_DIR/{plan-name}/ - Project must be configured (
.claude/testing.mdexists) - Plan status must be
readyorin_progress
Check prerequisites:
ls "$PLANS_DIR/{plan-name}/_plan.md" .claude/testing.md 2>/dev/null
If not found, output error and stop.
- Must be on the correct feature branch
Verify the current branch matches feature/{plan-name}:
git branch --show-current
If the current branch is not feature/{plan-name}:
- Output an error explaining which branch is expected
- Ask the user if they'd like to check out
feature/{plan-name} - Do NOT proceed until on the correct branch
Project Configuration
Execution Algorithm
Step 0: Suggest Unattended Completion via /goal
Claude Code's built-in /goal command keeps a session working toward a
verifiable end state — its evaluator runs after each turn and pushes execution
to continue until the condition is met. Only the user can set a goal (/goal
is a user-typed command and cannot be invoked from a skill), so surface a
copy-pasteable tip and continue immediately. This is informational, never a
gate — do not wait for a response.
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.
- 2d ago First seen · 564 lines · 72 tokens per session scan A 0cbee5d28435
plan-orchestrate is a skill published in the GitHub repository markshust/hcf (67 stars, last pushed 8d ago), licensed MIT. It adds 72 tokens to every session and 5,583 once invoked, about $0.0004 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-30.
Other skills, from other repositories
test-driven-development
TDD: enforce RED-GREEN-REFACTOR, tests before code.
engineering-workflow
可靠工程工作流的执行细则——探索→计划→TDD→系统化调试→代码审查→完成前验证。供方法论教练在开发任务中逐步引导。.
implement
Implement a technical design by decomposing it into dependency-ordered vertical slices, executing each with TDD red-green, reviewing each via an isolated sub-agent, and persisting progress to a state file so work survives session restarts. Use when the user has a tech design (doc or settled conversation) and says…
test-driven-development
TDD: enforce RED-GREEN-REFACTOR, tests before code.
write-eval
Write a live eval for new or changed runner/agent behavior using red/green TDD plus a falsification check that proves the eval fails when the behavior is broken. Use whenever you add or modify behavior that should be covered by an eval, when asked to "write an eval", "add an eval", "cover this with an eval", or after…
rust-testing
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.