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/hack-dance/hack/hack-clinpx skills add hack-dance/hack --skill hack-cligit clone --depth 1 https://github.com/hack-dance/hackWhat 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.00066 | $0.03590 |
| Opus 5 | $0.00033 | $0.01795 |
| Sonnet 5 | $0.00013 | $0.00718 |
| Haiku 4.5 | $0.00007 | $0.00359 |
Grade A, and why
hack-cli 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hack CLI
Use hack as the primary interface for local-first development.
Integration freshness
- These instructions were generated by hack CLI v3.5.0; treat cached rules from another version as potentially stale.
- At session start, audit project and global integrations with
hack setup sync --all-scopes --check. - If anything is stale, missing, or deprecated, run
hack setup sync --all-scopes, then reload the agent session so cached instructions are replaced. - Never copy or hand-edit generated Hack rules to refresh them; update the CLI and run the sync command.
- Content revision:
1319d93c89c3(version alone is not a freshness guarantee).
Product boundary
- Supported v3 surface: project init, up/down/restart, open, logs, env, host exec/shell, sessions, doctor, and daemon.
- Removed surfaces: hosted auth/account/org/team flows, web dashboard, built-in GitHub workflows, and built-in Linear sync.
- Experimental and unsupported: remote/gateway/node/dispatch commands. They are hidden from default help (list with
hack help --all) and warn on use; do not use them unless explicitly requested.
Operating rules
- Prefer
hackover rawdocker/docker composefor project workflows. - Do not start/stop services from Docker Desktop UI for
hack-managed projects. - Treat
.hack/.internaland.hack/.branchas hack-managed artifacts; do not hand-edit generated files there. - Use
--jsonfor machine-readable output when available;hack up/down/restart/doctor --jsonemit an{ok, data | error: {code, message}}envelope with stable E_* error codes. - Scripted/agent runs: pass
--no-interactive(or setHACK_NO_INTERACTIVE=1) so commands never block on prompts — they apply documented defaults or fail fast with E_INTERACTIVE_REQUIRED. - Use MCP only when shell access is unavailable.
- If runtime state looks wrong, run
hack doctor, thenhack doctor --fixbefore manual repair.
Core objects
- Project: a repo with
.hack/config + compose file. - Service: a compose service (e.g. api, web, worker).
- Instance: a running project; branch instances are separate copies started with
--branch.
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 · 213 lines · 66 tokens per session scan A f0ee995ea615
hack-cli is a skill published in the GitHub repository hack-dance/hack (8 stars, last pushed 20d ago), licensed MIT. It adds 66 tokens to every session and 3,590 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…