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 skills add midFang/ai-agent-skills-workflow --skill plan-to-issues-csvgit clone --depth 1 https://github.com/midFang/ai-agent-skills-workflowWrote 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/midfang/ai-agent-skills-workflow/plan-to-issues-csv)<a href="https://agentmods.dev/skills/midfang/ai-agent-skills-workflow/plan-to-issues-csv"><img src="https://agentmods.dev/badge/skills/midfang/ai-agent-skills-workflow/plan-to-issues-csv/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/midfang/ai-agent-skills-workflow/plan-to-issues-csv"><img src="https://agentmods.dev/badge/skills/midfang/ai-agent-skills-workflow/plan-to-issues-csv.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.00124 | $0.00641 |
| Opus 5 | $0.00062 | $0.00320 |
| Sonnet 5 | $0.00025 | $0.00128 |
| Haiku 4.5 | $0.00012 | $0.00064 |
Grade A, and why
plan-to-issues-csv 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 8d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan To Issues CSV
Use this skill as the replacement for the deprecated custom prompt /prompts:plan_to_issues_csv.
Invocation
Preferred explicit trigger:
$plan-to-issues-csv plan/2026-03-31_10-00-00-login-flow.md
Natural-language triggers:
把这个 plan 转成 issues csv从 plan 生成可维护的 issues 快照
Input Rules
- Accept an optional plan file path.
- If no path is provided, use the latest
plan/*.mdin the current workspace. - Read the plan file first, then read only the minimum referenced files needed to fill gaps.
Output Rules
- Always write a uniquely named snapshot under
issues/. - Never create or update
issues/issues.csv,issues.csv, or any other fixed summary CSV. - Write the file as UTF-8 with BOM for Excel compatibility.
- Keep the CSV maintainable: default to one issue row per plan phase unless a phase clearly contains multiple independent workstreams.
- Target roughly 5-30 rows.
Fixed Header
Use this exact header order:
id,priority,phase,area,title,git_message,description,acceptance_criteria,test_mcp,review_initial_requirements,review_regression_requirements,dev_state,review_initial_state,review_regression_state,git_state,owner,refs,notes
Row Defaults
dev_state:未开始review_initial_state:未开始review_regression_state:未开始git_state:未提交owner: emptynotes: emptyrefs: must not be empty; usepath:lineand separate multiple refs with;
Validation
Before finishing:
- Ensure the CSV is parseable.
- Ensure every row has the full header width.
- Ensure all state columns only use the allowed enum values.
- Ensure every row has a non-empty
refsvalue.
Reply Shape
Return only the essentials:
- Snapshot path
- Row count
- Any risks such as Excel/WPS file locks or limited source detail
- The next recommended command in skill form:
$plan-csv-execute <snapshot-path>
If file writes are blocked, return the full CSV in a code block and state the target path plus the UTF-8 BOM requirement.
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.
- 8d ago First seen · 68 lines · 124 tokens per session scan A 4b2f4a9e436e
plan-to-issues-csv is a skill published in the GitHub repository midFang/ai-agent-skills-workflow (2 stars, last pushed 2mo ago), licensed MIT. It adds 124 tokens to every session and 641 once invoked, about $0.0006 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.