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/mtuska/hacknplan-mcp/hacknplannpx skills add mtuska/hacknplan-mcp --skill hacknplangit clone --depth 1 https://github.com/mtuska/hacknplan-mcpWhat 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.00091 | $0.01103 |
| Opus 5 | $0.00046 | $0.00551 |
| Sonnet 5 | $0.00018 | $0.00221 |
| Haiku 4.5 | $0.00009 | $0.00110 |
Grade A, and why
hacknplan 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HacknPlan project management
This skill drives the @mtuska/hacknplan-mcp server. Its tools wrap the HacknPlan
API v0. Prefer these tools over guessing; HacknPlan is id-driven, so resolve
names to ids first.
Orientation (do this before acting)
hacknplan_whoami— confirm the API key works (run once if unsure).list_projects— get project ids.get_project— one call that rolls up a project's stages, categories, importance levels, and boards. You almost always need this before creating or moving work items, because creates require ids from it.
Resolving names → ids
The user will say "move the Login bug to Done", not give ids. Resolve first:
find_work_items(project_id, query, …)— free-text + facet search; the fastest way to turn a remembered title into aworkItemId. Use its result's id withupdate_work_item/get_work_item/ etc.- For stages/categories/importance/tags, read them from
get_project(or thelist_*tools) and match by name to get the id.
Common workflows
- Create a task or story —
create_work_item. Requirestitle+importance_level_id; tasks also needcategory_id. New items land in the first stage — passstage_idto place them elsewhere. Useparent_idto nest a task under a user story. - Break a feature down —
plan_featurecreates a user story plus its child tasks (and optional per-task checklists) in one call. Prefer it over manycreate_work_itemcalls. - Move / edit a work item —
update_work_item. It can re-stage, retitle, re-prioritize (importance_level_id), recategorize, re-estimate (estimated_cost), set due/start dates, block/unblock, retag, reassign (assigned_user_idsreplaces the whole set), and move board/milestone. Send only the fields you're changing. - Checklists —
add_subtask/list_subtasks/update_subtask(setis_completed). - Comments, tags, assignment —
add_comment,attach_tag/detach_tag,assign_user/unassign_user. - Dependencies —
add_dependency(successor blocked by predecessor),list_dependencies,remove_dependency. - Time tracking —
log_work,list_work_logs.
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 · 82 lines · 91 tokens per session scan A 624793cb9ba2
hacknplan is a skill published in the GitHub repository mtuska/hacknplan-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 91 tokens to every session and 1,103 once invoked, about $0.0005 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
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
setup-matt-pocock-skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.