Instructions for managing HacknPlan, a project-management service for boards, sprints, milestones, and work items such as tasks and user stories.

It is for viewing, searching, creating, updating, organizing, estimating, assigning, and tracking HacknPlan work.

It helps translate project names into the IDs HacknPlan requires and keeps work-item changes tied to the right project structures.

How mtuska/hacknplan-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to mtuska/hacknplan-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/mtuska/hacknplan-mcp/main/.claude/skills/hacknplan/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/mtuska/hacknplan-mcp

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mtuska/hacknplan-mcp/hacknplan/github.svg)](https://agentmods.dev/skills/mtuska/hacknplan-mcp/hacknplan)

Your own site

<a href="https://agentmods.dev/skills/mtuska/hacknplan-mcp/hacknplan"><img src="https://agentmods.dev/badge/skills/mtuska/hacknplan-mcp/hacknplan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/mtuska/hacknplan-mcp/hacknplan"><img src="https://agentmods.dev/badge/skills/mtuska/hacknplan-mcp/hacknplan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 91 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,103 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What 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.1	$0.00091	$0.01103
Opus 5.5	$0.00036	$0.00441
Sonnet 5.5	$0.00018	$0.00221
Haiku 4.5	$0.00009	$0.00110

Measured 2mo ago against content hash 624793cb9ba2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.claude/skills/hacknplan/SKILL.md · 82 lines

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 a workItemId. Use its result's id with update_work_item / get_work_item / etc.
For stages/categories/importance/tags, read them from get_project (or the list_* tools) and match by name to get the id.

Common workflows

Create a task or story — create_work_item. Requires title + importance_level_id; tasks also need category_id. New items land in the first stage — pass stage_id to place them elsewhere. Use parent_id to nest a task under a user story.
Break a feature down — plan_feature creates a user story plus its child tasks (and optional per-task checklists) in one call. Prefer it over many create_work_item calls.
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_ids replaces the whole set), and move board/milestone. Send only the fields you're changing.
Checklists — add_subtask / list_subtasks / update_subtask (set is_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.

Read the full file on GitHub · 82 lines

Changes

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.

2mo ago First seen · 82 lines · 91 tokens per session scan A 624793cb9ba2

Subscribe to this mod's changes

hacknplan is a skill published in the GitHub repository mtuska/hacknplan-mcp (0 stars, last pushed 4mo ago), licensed MIT. It adds 91 tokens to every session and 1,103 once invoked, about $0.0004 per session on Opus 5.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.

Project management

hacknplan next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
hacknplanmtuska/hacknplan-mcp	Skill	0	4mo ago	MIT	A	91	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code

hacknplan-mcp: Skill for Claude Code