Borrowing it
Nothing to install: this file belongs to hlalljie/agent-workflow-presets. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hlalljie/agent-workflow-presets/main/.cursor/skills/plan-issues/SKILL.mdgit clone --depth 1 https://github.com/hlalljie/agent-workflow-presetsWrote 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.
[](https://agentmods.dev/skills/hlalljie/agent-workflow-presets/plan-issues)<a href="https://agentmods.dev/skills/hlalljie/agent-workflow-presets/plan-issues"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/plan-issues/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.
<a href="https://agentmods.dev/skills/hlalljie/agent-workflow-presets/plan-issues"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/plan-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00070 | $0.01314 |
| Opus 5.5 | $0.00028 | $0.00526 |
| Sonnet 5.5 | $0.00014 | $0.00263 |
| Haiku 4.5 | $0.00007 | $0.00131 |
Grade A, and why
plan-issues 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 19d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan issues
How plans and issues map
The mapping is loose and many-to-many. A plan can have no issue, one tracking issue, an issue per phase, or a mix. A phase can have zero, one, or several issues, and one issue can cover several phases. Nothing requires one issue per phase.
A plan that is really one issue gets one plan-level issue that covers every phase. Earlier phase commits Refs it, and the commit that finishes the plan's last phase Closes it.
The plan owns scope, phases, and tasks. The issue is where discussion happens, and its open or closed state is set by the Closes #N commit (commit skill). Do not copy plan status into an issue or issue status into the plan.
Links live in the plan, in an Issues: line: under the plan title for plan-level issues, and under a phase heading for phase-level ones (after Completed: if that line exists). A plan-level line covers every phase that has no line of its own. Format: Issues: [#12](https://github.com/<owner>/<repo>/issues/12), [#13](https://github.com/<owner>/<repo>/issues/13). The full URL keeps links portable if the tracker changes.
No Issues: line means not decided yet. Issues: none means decided: no issue. Under the plan title it covers the whole plan, and under a phase heading it covers that phase. Write it when the user says a plan or phase needs no issue; the user can also write it by hand.
Approval
Creating issues, and the standard labels they need, runs without asking. The project owner gave standing approval for this, and it covers only creating issues and those labels in the current repo, which is the exception to data-safety.mdc for this skill alone. In careful mode, state what will be created and wait for approval, as that mode requires (careful).
When to use
- run-task-loop is about to start a phase, and neither that phase nor the plan has an
Issues:line. - The user asks to create or link issues for a plan, a phase, or several phases.
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.
- 19d ago First seen · 53 lines · 70 tokens per session scan A d9694e7ceea3
plan-issues is a skill published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 20d ago), licensed MIT. It adds 70 tokens to every session and 1,314 once invoked, about $0.0003 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-10-10.
Other skills, from other repositories
work-on-ticket
Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKETID]" or similar phrases.
cast-plan
Turn a request into a plan the team can review before code exists. Explores the codebase, searches prior sessions and recorded decisions for earlier attempts, interviews the user on the open questions, then writes a codecast plan with tasks and dependencies ready for orchestrate. Use when work has several parts, when…
cast-org
Talk through the organization of agents and people around this work with the person, in this session: who reports to whom, what each role looks after, where their sessions go. Reads what the code and the sessions say before it trusts a plan or a task, asks what the records cannot settle, and posts each agreed change…
cast-handoff
Package the current work so the next session or a teammate can continue without reading this thread. Writes the decisions, the direction, what is verified, open questions and ordered next steps as a shared doc, pins the state, and optionally forks, spawns or hands the work to a session. Use before stopping, before a…
cast-loop
Run an autonomous loop that works through a queue of tasks one fresh session at a time, with verification as the gate and a human decision at merge. Sets up a recurring trigger that spawns a session per ready task, a precheck that spends nothing when the queue is empty, and the rules each run follows. Use for a…
cast-conflicts
Before editing or fanning out work, find the live sessions on this repository that are changing the same files, show what they changed, and warn them. Use before starting a task that touches shared files, before spawning workers, or when asked who else is working on this.