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-createnpx skills add markshust/hcf --skill plan-creategit 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.00171 | $0.05087 |
| Opus 5 | $0.00086 | $0.02544 |
| Sonnet 5 | $0.00034 | $0.01017 |
| Haiku 4.5 | $0.00017 | $0.00509 |
Grade A, and why
plan-create 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 — 493 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Create
Transform feature requests into structured plans with task breakdowns, dependencies, and TDD requirements for parallel autonomous execution.
Project Architecture
Execution Flow
Phase 0: Pre-plan hook
Run this once, at the very start, before Phase 1 discovery.
Run the pre-plan hook.
Run the discovery script — never enumerate agent files by hand:
"{skill-base-dir}/../../hooks/discover-hooks.sh" --hook=pre-plan
{skill-base-dir} is the Base directory for this skill value stated when this skill loaded. ${CLAUDE_PLUGIN_ROOT} is not available in a skill's Bash calls.
- Exit 0, empty stdout → empty hook. This is the default. Return immediately: print nothing, spawn nothing, say nothing about the hook at all, and proceed to Phase 1. Do not narrate that the script returned no agents — that is the narration
HOOKS.mdforbids. - Exit 0, output → print the output verbatim as the resolved agent order, then spawn each listed agent in order per its
mode. - Any non-zero exit → stop. Surface the script's stderr verbatim and do not continue planning. Exit 3 means an agent file declares an invalid
phaseormode; exit 4 means enrollment drifted. Neither is an empty hook. If the script is missing or not executable, that is also a hard stop — there is no fallback, and you must not reconstruct the routine by hand.
Capture the enrollment fingerprint now, for Phase 6's drift check:
"{skill-base-dir}/../../hooks/discover-hooks.sh" --fingerprint
Hold that value. A fingerprint is only ever produced by running the script — never reconstruct, abbreviate, or recall one from memory. If it is not to hand at Phase 6, re-run the command and say so. A hallucinated digest makes every later check fail with bogus drift and bricks the plan.
IMPORTANT — no plan name exists yet. The pre-plan hook fires before Phase 1 discovery. The plan name and plan directory are not created until Phase 3, so there is no plan name to pass. Each pre-plan agent receives only:
- The raw feature request (the user's verbatim ask).
- The project's architecture context:
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 · 493 lines · 171 tokens per session scan A 9eaae5f7f77a
plan-create is a skill published in the GitHub repository markshust/hcf (67 stars, last pushed 7d ago), licensed MIT. It adds 171 tokens to every session and 5,087 once invoked, about $0.0009 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
knack-interview
Conduct the Knack 6-phase interview with a user to author a new skill. Load this skill when the user wants to teach you a recurring task they do and have it become a reusable Knack skill (e.g. "use knack to capture how I triage support tickets").
openalex
Use when the user asks about academic literature, research papers, scholarly works, authors, citations, institutions, journals, or any academic metadata. Trigger when users want to search for papers, find author profiles, track citations, discover related works, or explore academic topics. Also use when users mention…
stfu
Use this skill when the user wants terse, direct responses with no preamble, recap, filler, or unnecessary explanation. Supports persistent toggling with /stfu on and /stfu off. Applies to answers, writing, editing, commands, code changes, summaries, and any interaction where minimal output is preferred.
agency-os
Notion-as-source-of-truth dispatch board. Status flow Suggestion→Discussion→To-Do→In Progress→Done with subtasks, recurring tasks, deps, batch agent execution. Trigger: 'suggest X', 'discuss X', 'approve', 'start X', 'run todo', 'mark X done', 'kill X', 'next', 'capture this to Notion', 'agency-os status'.
knack-installer
Install Knack on the user's machine. Load this skill when the user asks to install Knack, set up Knack, get started with Knack, or expresses interest in managing AI skills with version control. Handles macOS, Linux, and Windows.
clawallex-skill
Pay for anything with USDC — virtual cards for any online checkout.