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-writingnpx skills add evoelsewhere/evoflux --skill work-writinggit 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.00070 | $0.00559 |
| Opus 5 | $0.00035 | $0.00280 |
| Sonnet 5 | $0.00014 | $0.00112 |
| Haiku 4.5 | $0.00007 | $0.00056 |
Grade A, and why
work-writing 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write professional content
Make the audience's next action easier without changing the underlying facts. Treat missing evidence as a visible gap, not an invitation to invent detail. Do not load bundled references or templates when this skill activates.
Establish the writing contract
- Identify audience, relationship and authority, desired action, channel, tone, length, confidentiality, and deadline.
- Establish the source of truth: supplied facts, approved decision, research, analysis, policy, or prior draft. Separate fixed facts from negotiable framing.
- Choose the genre based on audience behavior, not the requested filename. A decision memo, customer notice, proposal, and status update need different emphasis even when all are delivered as documents.
Draft for action
Put the conclusion, request, or material change where the audience expects it. Use the remaining structure to answer only what they need to decide or act: context, evidence, consequences, requested action, owner, and timing.
Use concrete subjects and verbs, stable terminology, meaningful headings, and paragraphs that advance one idea. Preserve citations next to material claims. Distinguish fact, interpretation, recommendation, commitment, and open question.
For a new brief or memo with no required house template, copy assets/brief-template.md and remove unused sections. Do not force emails, announcements, or short updates into the template.
Revise and risk-check
Read references/editorial-checklist.md only for executive, external, policy, incident, legal-adjacent, or high-stakes content, and whenever the draft contains numbers, dates, commitments, or sensitive claims.
Remove repetition, throat-clearing, unsupported emphasis, hedging that hides the conclusion, and detail that belongs in an appendix. Check names, dates, numbers, units, links, commitments, confidentiality, accessibility, and tone for the power relationship.
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 · 59 lines · 70 tokens per session scan A 59a0c24822e2
work-writing is a skill published in the GitHub repository evoelsewhere/evoflux (5 stars, last pushed 6d ago), licensed Apache-2.0. It adds 70 tokens to every session and 559 once invoked, about $0.0003 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
rove
Use when controlling Rove tasks, parallel coding attempts, hosted agent sessions, task lifecycle, or the daemon-owned issue tracker from a shell. Also the ONLY channel for messaging another agent session on this machine — rove api send, never a peer/MCP side channel.
E2E Testing Nori Skillsets Subcommands
Use when you need to interactively test a nori-skillsets CLI subcommand end-to-end via tmux, with full filesystem isolation.
changelog-generator
Draft Rove release notes as Changesets. Writes user-facing entries as .changeset/.md files for @sma1lboy/rove (consumed into packages/kobe/CHANGELOG.md at release time). Use when the user asks for "changelog", "release notes", "what changed", "add a changeset", or before cutting a version. Enforces Rove's no-soft-wrap…
token-saver-config
Configure and diagnose token-saver compression settings. Use when the user asks about adjusting compression levels, checking processor status, debugging hook issues, or reviewing savings statistics.
issue-review
Triage a copperhead GitHub issue, attempt reproduction, and check it against the spec. Use when the user asks to review an issue, e.g. /issue-review 42 or /issue-review .
openai-docs
Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, latest/current/default-model prompting guidance, or model upgrade and prompt-upgrade guidance; use…