Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/duc01226/EasyPlatformnpx agentmods add skills/duc01226/easyplatform/workflow-planned-workWrote 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/duc01226/easyplatform/workflow-planned-work)<a href="https://agentmods.dev/skills/duc01226/easyplatform/workflow-planned-work"><img src="https://agentmods.dev/badge/skills/duc01226/easyplatform/workflow-planned-work/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/duc01226/easyplatform/workflow-planned-work"><img src="https://agentmods.dev/badge/skills/duc01226/easyplatform/workflow-planned-work.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.00050 | $0.05951 |
| Opus 5.5 | $0.00020 | $0.02380 |
| Sonnet 5.5 | $0.00010 | $0.01190 |
| Haiku 4.5 | $0.00005 | $0.00595 |
Grade A, and why
workflow-planned-work 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 3d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex compatibility note:
- Invoke
$skill-name: load the registered.agents/skills/<name>/SKILL.mdand execute it with Codex tools; no separateSkilltool or Claude mode switch is needed. Author.claude/**; mirrors are generated.- Track steps before execution and keep progress/evidence current. Explicit skill requests execute their protocol. Use the native question tool for required questions.
- Map foreign tool names to available host capabilities. A name mismatch needs no approval; an actually unavailable required capability stops with its step/evidence and a user question before adaptation.
- Subagent authorization: when a skill is user-invoked or AI-detected and its protocol requires subagents, that skill activation authorizes use of the required
spawn_agentsubagent(s) for that task.- Preserve protocol order unless the user approves a deviation. Workflows use
$start-workflow: gates stay fixed; other steps may flex with logged reasons and evidence.
Workflow Calls and Todo Bootstrap
Read the registry → workflows.workflow-planned-work together with this skill. Call $start-workflow workflow-planned-work to resolve the selected mode, pre-actions and fingerprint.
Todo FIRST: before triage, analysis or step execution, create one todo per phase of the selected mode, in order, listing every occurrence of that phase as a line, including conditional/optional ones (a mode that declares no phases gets one todo per occurrence); preserve occurrence IDs, roles and barrier groups. Use native todo tools or an equivalent persistent ledger. Then mark the first todo in_progress; close each step line with its run or skip evidence, and complete a phase todo only when every line is closed and its applicable exit gates hold.
Mode selection and registry loading prepare tracking; any 'first action' below means the first substantive action after this bootstrap.
Call each step skill: read its linked SKILL.md and execute its protocol through the active host with the registry args. Reading or naming a skill alone is not execution. Required gates and core/optional flex follow the linked start-workflow Step Execution Protocol; keep this skill's quality gates, loops and evidence requirements.
Conditions: load each occurrence's registry applicability.when and skipReason verbatim, and record its run/skip evidence through the linked start-workflow protocol. Do not silently omit a todo or turn a conditional skill into an unconditional call; close, in one batch at triage, the todos whose condition is already false there. Declared parallel groups retain their all-return barrier.
Explicit step-skill calls by mode (registry order; roles and conditions remain owned by the registry):
- Mode
idea-to-tasks:$web-research --chain=deep-dive(optional; conditional) →$brainstorm(optional; conditional) →$initiative(core) →$spec [mode=discovery](optional; conditional) →$work-item --mode=review(optional; conditional) →$domain-analysis(optional; conditional) →$why-review(optional; conditional) →$spec [mode=draft](optional; conditional) →$spec [mode=tests](optional; conditional) →$work-item --mode=review --type=spec-tests(optional; conditional) →$spec [mode=clarify](optional; conditional) →$scenario(optional; conditional) →$plan(optional; conditional) →$work-item --mode=refine(core) →$work-item --mode=review --type=task --fix-loop(gate) →$work-item --mode=challenge --reuse=task-review(optional; conditional) →$work-item --mode=story(core) →$work-item --mode=dor --reuse=task-review(gate) →$prioritize(optional; conditional) →$design-spec(optional; conditional) →$work-item --mode=review --type=design(optional; conditional) →$work-item --mode=mockup --explore(optional; conditional) →$docs-manager --mode=update(optional; conditional) →$feature-presentation(optional; conditional) →$workflow-end(gate) →$watzup(optional; conditional) Phase todos: Discover (7) → Specify (5) → Plan (11; exit review-converged, spec-synced) → Close (3; exit run-closed)
- Mode
idea-to-spec:$web-research --chain=deep-dive(optional; conditional) →$brainstorm(optional; conditional) →$spec [mode=discovery](optional; conditional) →$scenario(optional; conditional) →$domain-analysis(optional; conditional) →$why-review(optional; conditional) →$initiative(optional; conditional) →$spec [mode=draft](core) →$spec [mode=tests](core) →$work-item --mode=review --type=spec-tests --fix-loop(gate) →$design-spec(optional; conditional) →$work-item --mode=review --type=design(optional; conditional) →$spec [mode=clarify](gate) →$why-review(optional; conditional) →$docs-manager --mode=update(optional; conditional) →$feature-presentation(optional; conditional) →$workflow-end(gate) →$watzup(optional; conditional) Phase todos: Discover (3) → Specify (12; exit review-converged) → Close (3; exit run-closed)
- Mode
spec-to-tasks:$investigate(core) →$spec [mode=index](optional; conditional) →$domain-analysis(optional; conditional) →$why-review(optional; conditional) →$spec [mode=clarify](gate) →$scenario(optional; conditional) →$plan(optional; conditional) →$work-item --mode=refine(core) →$work-item --mode=review --type=task --fix-loop(gate) →$work-item --mode=challenge --reuse=task-review(optional; conditional) →$work-item --mode=story(core) →$work-item --mode=dor --reuse=task-review(gate) →$prioritize(optional; conditional) →$design-spec(optional; conditional) →$work-item --mode=review --type=design(optional; conditional) →$work-item --mode=mockup --explore(optional; conditional) →$docs-manager --mode=update(optional; conditional) →$feature-presentation(optional; conditional) →$workflow-end(gate) →$watzup(optional; conditional) Phase todos: Discover (4) → Specify (2) → Plan (11; exit review-converged, spec-synced) → Close (3; exit run-closed)
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 149 lines · 50 tokens per session scan A adf02026f408
workflow-planned-work is a skill published in the GitHub repository duc01226/EasyPlatform (12 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 5,951 once invoked, about $0.0002 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-18.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…