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 xcaeser/work-skill --skill work-helpgit clone --depth 1 https://github.com/xcaeser/work-skillWrote 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/xcaeser/work-skill/work-help)<a href="https://agentmods.dev/skills/xcaeser/work-skill/work-help"><img src="https://agentmods.dev/badge/skills/xcaeser/work-skill/work-help/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/xcaeser/work-skill/work-help"><img src="https://agentmods.dev/badge/skills/xcaeser/work-skill/work-help.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.00035 | $0.00861 |
| Opus 5.5 | $0.00014 | $0.00344 |
| Sonnet 5.5 | $0.00007 | $0.00172 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
work-help 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work / 11. Help
Show the Work skill family directly. Do not inspect the repository, spawn agents, create goals, or run a task. Do not make the user remember subcommands.
When explaining the shared standard, use the $work-quality description below;
do not resolve or read files outside this skill folder.
Work skills
| Skill | Use it for |
|---|---|
$work |
Delegate and integrate a free-form implementation task |
1. $work-init |
Start and verify a new project |
2. $work-ideate |
Brainstorm with a rigorous, question-by-question creative sparring partner |
3. $work-plan |
Build a detailed read-only plan with Sol xhigh |
4. $work-test |
Inspect real behavior, add justified tests, and report omissions and bugs |
5. $work-concern |
Surface evidence-backed concerns in the current implementation without editing |
6. $work-checklist |
Capture conversation as a checklist, then optionally execute it |
7. $work-audit |
Audit risks with Sol xhigh and produce an executor-ready fix plan |
8. $work-clean |
Analyze code smells with Sol xhigh and produce an executor-ready cleanup plan |
9. $work-quality |
Pass the Work golden rules directly into the conversation |
10. $work-status |
Show the current goal, agents, evidence, and next action |
11. $work-help |
Show this map |
Model shorthand
Work / 2. Ideate: interactive conversation; no agents or model selection.Work / 4. Test: parent-led test implementation; no agents or coverage target.Work / 5. Concern: lightweight read-only inspection; no agents or fix plan.Work / 6. Checklist: Capture returns a checklist only; Execute registers one parent-owned goal. No agents.Work / 3. Plan,7. Audit, and8. Clean: one read-only Sol xhigh analyst; no edits.- Plans are executor-agnostic and detailed enough for a lower-capability model with no hidden context.
- Terra Low handles small mechanical chores; Terra Medium handles structured exploration or extraction.
mixlets the parent choose Sol or Terra per assignment and explain the split before launch.- Executors use
fork_turns: none, narrow ownership, and compact artifact-first handoffs to control token use. $work: automatic routing (Sol Low for ordinary work) unless the user proposes a count, profile, or effort. Advanced form:$work [N] [sol|terra|mix] [effort] <task>. Work explains its recommendation and waits for confirmation; it never invents assignments to satisfy an oversized count.
What ships with it
1 file 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.
- 1mo ago First seen · 56 lines · 35 tokens per session scan A 6b0b7097be46
work-help is a skill published in the GitHub repository xcaeser/work-skill (2 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 861 once invoked, about $0.0001 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
cortex-init
Set up Cortex by discovering the user's existing systems and generating a personalized Workflow Registry from them. Use when the user runs /cortex-init, says "set up cortex", "adopt my tools into cortex", "build my registry", or right after installing Cortex for the first time.
cortex-learn
Detect routing patterns in the Cortex log and surface candidate Decision Shortcuts for cortex.md. Use when the user asks for routing patterns, wants to tune cortex defaults, or says "/cortex-learn".
cortex-reroute
Mark the last Cortex routing decision as corrected and record the route the user actually wanted. Use when the user says "reroute", "actually use X", "should've been Y", or types "/cortex-reroute".
cortex-log
Show recent Cortex routing decisions with reasoning trail. Use when the user asks what routes have been picked, wants to audit recent routing decisions, or says "show cortex log" / "what did cortex do" / "/cortex-log".
code-review
Orchestrate an adaptive multi-agent review of a pull request or local change that builds a structural and semantic brief, assigns risk-based reviewer lanes at runtime, challenges and deduplicates their findings, verifies each one, and renders an evidence-backed review. Use when a pull request or local change needs…
tech-debt-audit
Audit a whole repository or subsystem for technical debt with at most four non-overlapping read-only subagents, lead verification, and interest-over-principal ranking, and produce an evidence-backed debt register. Use when the user wants to find, size, or prioritize existing debt across a codebase; not for reviewing…