What is plan-csv-execute?

A workflow for implementing work from an issues CSV file. A CSV is a plain table of issue records; the workflow treats that file as the task list and records implementation, review, validation, and local commits.

Use it to execute unfinished issues from a correctly formatted CSV, including code changes, reviews, tests or other validation, and local Git commits.

It keeps development tied to one explicit list of issues and closes the loop from coding through checks. It also prevents accidental publishing by requiring local commits without pushing.

plan-csv-execute — Skill for Claude Code and Codex by midFang: A workflow for implementing work from an issues CSV…

Install

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.

agentmods

npx agentmods add skills/midfang/ai-agent-skills-workflow/plan-csv-execute

Any agent

npx skills add midFang/ai-agent-skills-workflow --skill plan-csv-execute

Clone the repo

git clone --depth 1 https://github.com/midFang/ai-agent-skills-workflow

Made for: Claude Code, Codex.

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/midfang/ai-agent-skills-workflow/plan-csv-execute.svg)](https://agentmods.dev/skills/midfang/ai-agent-skills-workflow/plan-csv-execute)

Your own site

<a href="https://agentmods.dev/skills/midfang/ai-agent-skills-workflow/plan-csv-execute"><img src="https://agentmods.dev/badge/skills/midfang/ai-agent-skills-workflow/plan-csv-execute.svg" alt="Measured on agentmods" height="20"></a>

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

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

Security scan A 0 findings. Scan, not verified.

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	$0.00085	$0.00829
Opus 5	$0.00043	$0.00415
Sonnet 5	$0.00017	$0.00166
Haiku 4.5	$0.00009	$0.00083

Measured 5d ago against content hash a58989b436a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

plan-csv-execute 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 5d 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.

plan-csv-execute/SKILL.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Issues CSV Execute

Use this skill as the replacement for the deprecated custom prompt /prompts:issues_csv_execute.

Invocation

Preferred explicit trigger:

$plan-csv-execute issues/2026-03-31_10-10-00-login-flow.csv

Natural-language triggers:

按这份 issues csv 执行
根据 CSV 闭环开发直到提交

Core Rules

Treat the user-supplied CSV as the only state source.
Do not create or sync any extra summary CSV files unless the user explicitly asks.
Default goal: move every unfinished row to a closed local state.
Each issue must be handled as a full loop:
- implement
- review
- validate
- local git commit
Never push.
By default, do not add issues/*.csv, plan/, *.md, or other process documents to commits.
Use update_plan for multi-step execution runs.

Required Header

Expect this exact header:

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

If the CSV does not match, stop and ask the user to regenerate or repair the CSV first.

Issue Selection Order

Finish hanging work first: rows with git_state=未提交 and dev_state=进行中|已完成.
Then prefer unfinished rows by P0 -> P1 -> P2.
Write a short picked_reason: note into the row when selecting it.

Per-Issue Workflow

Re-state the target row: id, title, acceptance criteria, and main risks.
If acceptance_criteria, review requirements, test_mcp, or refs are incomplete, update the CSV first.
Set dev_state=进行中 and review_initial_state=进行中.
Read refs, gather the minimum code context, and implement only the work inside that row's boundary.
Run the most relevant tests or checks you can.
If full validation is not possible, record all of these in notes:
- validation_limited:<reason>
- manual_test:<steps>
- evidence:<what was verified>
- risk:<low|medium|high> <why>
Once the issue is genuinely ready, set:
- dev_state=已完成
- review_initial_state=已完成
- review_regression_state=已完成 when the available regression evidence is sufficient
Commit code-only changes with a message exactly equal to the row's git_message.
If the commit succeeds, set git_state=已提交.
If the commit fails, set git_state back to 未提交 and record blocked:git commit failed <reason> in notes.

Read the full file on GitHub · 83 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.

5d ago First seen · 83 lines · 85 tokens per session scan A a58989b436a0

Subscribe to this mod's changes

plan-csv-execute is a skill published in the GitHub repository midFang/ai-agent-skills-workflow (2 stars, last pushed 2mo ago), licensed MIT. It adds 85 tokens to every session and 829 once invoked, about $0.0004 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.

Commits Git and workflow Planning

create-pr

Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.

prisma/orm · 47 tokens

git-commit

Generate well-formatted git commit messages following conventional commit standards.

ThinkInAIXYZ/deepchat · 15 tokens

commit-push-pr

Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.

GCWing/BitFun · 68 tokens

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

commit

Commit current changes with a clear, descriptive message.

NVIDIA-NeMo/DataDesigner · 11 tokens

contributing

How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…

HugoRCD/evlog · 68 tokens