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 agentmods add skills/evoelsewhere/evoflux/work-planningnpx skills add evoelsewhere/evoflux --skill work-planninggit clone --depth 1 https://github.com/evoelsewhere/evofluxWhat 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.00076 | $0.00551 |
| Opus 5 | $0.00038 | $0.00275 |
| Sonnet 5 | $0.00015 | $0.00110 |
| Haiku 4.5 | $0.00008 | $0.00055 |
Grade A, and why
work-planning 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 2d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan coordinated work
Create an execution control surface, not a decorative list of phases. Every work item must produce an observable deliverable and unblock a named outcome. Do not load bundled references or templates when this skill activates.
Establish the planning contract
- Define outcome, accountable owner, deadline or time constraint, completion evidence, scope, and explicit non-goals.
- List constraints, stakeholders, dependencies, available capacity, existing commitments, and decisions that must precede execution.
- Mark unknown owner, date, or capacity as unknown. Do not fill gaps with invented assignments or estimates.
Build the plan
Break work into the smallest outcome-bearing slices that can be verified and handed off. Each slice needs:
- one accountable owner or an explicit owner gap;
- concrete deliverable and acceptance signal;
- prerequisite and downstream consumer;
- effort assumption or time constraint, where known;
- rollback, contingency, or recovery for risky operational change.
Order slices by dependency and risk. Put discovery and proof before commitments that depend on feasibility. Show the critical path, external handoffs, decision gates, and work that can proceed in parallel.
Read references/plan-quality-gates.md only for multi-team plans, fixed deadlines, rollout or migration work, external dependencies, or plans that need estimates.
Make risk operational
Track only risks that can materially change outcome, time, scope, or trust. For each, name cause, early signal, likelihood/impact, mitigation owner, contingency, and the point at which the plan changes.
Define a review cadence tied to evidence, not status theater. Reviews must be able to re-sequence, de-scope, stop, or escalate work.
Produce the artifact
When a durable plan is requested, copy assets/execution-plan.md and replace all placeholders. Adapt sections to the work; omit irrelevant ceremony rather than leaving empty headings.
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.
- 2d ago First seen · 62 lines · 76 tokens per session scan A fbbd7af3e9fc
work-planning is a skill published in the GitHub repository evoelsewhere/evoflux (5 stars, last pushed 5d ago), licensed Apache-2.0. It adds 76 tokens to every session and 551 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.
Other skills, from other repositories
kane-cli
Browser automation + AI test authoring via kane-cli - run browser objectives, generate & refine test scenarios/cases from a description, design requirement-linked test suites from a PRD/spec (assurance), parse NDJSON output, inspect logs, save runnable test.md. Use for any task requiring a real browser (navigate…
control-chrome
Control the user's Chrome browser for tasks that depend on existing Chrome state: tabs, logged-in sessions, or extensions. Prefer purpose-built connectors, APIs, or CLIs when available.
yutori-computer-use
Run local Mac desktop tasks with Yutori computer use. Use when the user wants to operate macOS apps, websites in a local browser, or cross-app workflows on the visible desktop.
vibesurfer
Agent-native headless browser. 20 primitives over a Unix-socket wire protocol. Real WKWebView (macOS), WebKitGTK 6 (Linux), or WebView2 (Windows) — all three engines CI-verified by 48 integration cells per platform. Optimistic concurrency via state tokens; tree-delta wire format; durable session/page/auth state in…
yutori-research
Execute deep web research on any topic using Yutori's research agents. Use for competitive analysis, market research, finding documentation, or answering complex questions that require synthesizing information from multiple sources.
yutori-browse
Automate browser tasks like form filling, data extraction, or multi-step web workflows. Use when the user needs to interact with websites that require clicking, typing, or navigation.