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-csv-executegit 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-csv-execute)<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/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-csv-execute"><img src="https://agentmods.dev/badge/skills/midfang/ai-agent-skills-workflow/plan-csv-execute.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.00085 | $0.00829 |
| Opus 5.5 | $0.00034 | $0.00332 |
| Sonnet 5.5 | $0.00017 | $0.00166 |
| Haiku 4.5 | $0.00009 | $0.00083 |
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 1mo 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 — 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_planfor 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=未提交anddev_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, orrefsare incomplete, update the CSV first. - Set
dev_state=进行中andreview_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_stateback to未提交and recordblocked:git commit failed <reason>innotes.
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.
- 1mo ago First seen · 83 lines · 85 tokens per session scan A a58989b436a0
plan-csv-execute is a skill published in the GitHub repository midFang/ai-agent-skills-workflow (2 stars, last pushed 4mo ago), licensed MIT. It adds 85 tokens to every session and 829 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-08-31.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
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…
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.