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/project-updatenpx skills add markshust/hcf --skill project-updategit 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.00033 | $0.05382 |
| Opus 5 | $0.00016 | $0.02691 |
| Sonnet 5 | $0.00007 | $0.01076 |
| Haiku 4.5 | $0.00003 | $0.00538 |
Grade A, and why
project-update 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 3d 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync a project's HCF configuration with the latest plugin defaults. Non-destructive — adds missing files, generates what's needed, and flags differences in existing ones.
Prerequisites
This skill requires that /project-setup has been run at least once. If CLAUDE.md and .claude/ don't exist, tell the user to run /project-setup first and stop.
Execution Steps
Step 1: Verify Project Is Configured
Check that the project has been set up:
ls CLAUDE.md .claude/ 2>/dev/null
If either is missing, stop and tell the user:
This project hasn't been set up yet. Run
/project-setupfirst.
Step 2: Inventory Expected Files
These are the files that project-setup creates. Check which exist:
| File | Source |
|---|---|
CLAUDE.md |
Generated from project context |
.claude/testing.md |
Generated from project context |
.claude/code-standards.md |
Generated from project context |
.claude/architecture.md |
Generated from project context |
.claude/pipeline.mdis legacy and is no longer an expected ongoing file. HCF now enrolls agents via frontmatter (see HOOKS.md). If a.claude/pipeline.mdexists, it is handled by the one-time migration in Step 3 — do not treat its absence as a missing file.
Collect the list of missing files. Do NOT act on them yet — just note them.
Step 3: Migrate Legacy pipeline.md to Frontmatter
This is a one-time migration from the legacy central registry (.claude/pipeline.md) to per-agent frontmatter enrollment (the model described in HOOKS.md). This step detects what needs to happen here; the actual changes are applied in Step 6 after a single confirmation.
3a. Detect the legacy file
Check whether .claude/pipeline.md exists:
ls .claude/pipeline.md 2>/dev/null
- Absent → the project is already on the frontmatter model. Record migration status as "no legacy
pipeline.md— already on frontmatter" and skip the rest of Step 3 entirely. There is nothing to migrate. - Present → continue to 3b.
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.
- 3d ago First seen · 270 lines · 33 tokens per session scan A 1185b730df7a
project-update is a skill published in the GitHub repository markshust/hcf (67 stars, last pushed 8d ago), licensed MIT. It adds 33 tokens to every session and 5,382 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-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.