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 Heyvhuang/ship-faster --skill workflow-execute-plansgit clone --depth 1 https://github.com/Heyvhuang/ship-fasterWrote 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/heyvhuang/ship-faster/workflow-execute-plans)<a href="https://agentmods.dev/skills/heyvhuang/ship-faster/workflow-execute-plans"><img src="https://agentmods.dev/badge/skills/heyvhuang/ship-faster/workflow-execute-plans/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/heyvhuang/ship-faster/workflow-execute-plans"><img src="https://agentmods.dev/badge/skills/heyvhuang/ship-faster/workflow-execute-plans.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Excessive Agency · line 45 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00071 | $0.00900 |
| Opus 5 | $0.00036 | $0.00450 |
| Sonnet 5 | $0.00014 | $0.00180 |
| Haiku 4.5 | $0.00007 | $0.00090 |
Grade A, and why
workflow-execute-plans 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 9d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executing Plans (Batch Execution + Checkpoints)
Goal
Reliably turn a "written plan file" into implementation results, avoiding drift or accumulated risk from doing everything at once.
Core strategy: Batch execution + pause for feedback after each batch.
Input/Output (Recommended for Chaining)
Input (pass paths only):
plan_path: Plan file (usually inrun_dir/03-plans/)repo_rootrun_dir
Output (persisted):
- Plan execution status:
logs/state.json(or03-plans/<plan>-status.md) - Per-batch verification evidence: append to the corresponding plan file or
05-final/summary
Execution Flow
Step 1) Read and Review Plan (Critical Review First)
- Read
plan_path - Review if the plan has these issues:
- Missing dependencies (packages to install/env vars/external services)
- Task granularity too large (can't verify, hard to rollback)
- Missing acceptance criteria or verification commands
- Obviously wrong task ordering
- If critical issues found: Stop first, present concerns as 1-3 bullet points, let human confirm before starting execution.
Rule: Don't "guess while doing". Clarify when plan is unclear.
Step 2) Batch Execution (Default 3 Tasks per Batch)
Execute the first 3 tasks from the plan, then stop and report.
For each task:
- Mark as
in_progress - Execute strictly per plan (don't expand scope)
- Run verification per plan (tests / build / typecheck / lint / manual verification steps)
- Mark as
completed
Status recording (choose one, prefer structured):
- Update task status in
logs/state.json - Or maintain checklist in
plan_path([ ]→[x]), recording verification results alongside
Step 3) Batch Report (Must Pause for Feedback)
After each batch, report three things:
- What changed: Which files changed/what was implemented (brief)
- Verification: What verification was run, what were the results (key info only, no long logs)
- Next batch: Which 3 tasks are next
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.
- 9d ago First seen · 95 lines · 71 tokens per session scan A 8477e64e9e35
workflow-execute-plans is a skill published in the GitHub repository Heyvhuang/ship-faster (339 stars, last pushed 24d ago), licensed MIT. It adds 71 tokens to every session and 900 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…