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 michaelcjoseph/agent-coding-setup --skill workgit clone --depth 1 https://github.com/michaelcjoseph/agent-coding-setupWrote 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/michaelcjoseph/agent-coding-setup/work)<a href="https://agentmods.dev/skills/michaelcjoseph/agent-coding-setup/work"><img src="https://agentmods.dev/badge/skills/michaelcjoseph/agent-coding-setup/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/michaelcjoseph/agent-coding-setup/work"><img src="https://agentmods.dev/badge/skills/michaelcjoseph/agent-coding-setup/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.00000 | $0.04063 |
| Opus 5.5 | $0.00000 | $0.01625 |
| Sonnet 5.5 | $0.00000 | $0.00813 |
| Haiku 4.5 | $0.00000 | $0.00406 |
Grade A, and why
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 2mo 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 — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/work
Pick the next pending task from a project's task list and drive it through the full implementation cycle: plan, implement, test, review, fix, simplify, and mark complete.
Usage
/work [project-name] [--auto]
If no argument is given, list all projects in docs/projects/ and ask the user which one to work on.
--auto (unattended mode): skips all user-interaction gates so one invocation sweeps the entire task list end-to-end. Specifically: step 2 skips the "confirm before proceeding" gate, Phase 1 skips Plan Mode entirely (still does exploration and writes the plan to the turn output for the transcript record, but does not call EnterPlanMode/ExitPlanMode since those require human approval), step 15 creates one git commit per completed task (using the release-notes agent to draft the message) without pausing for approval, and step 16 auto-continues to the next unchecked task without asking. Hard stops (step 2 empty list, step 9 caused-by-diff failures unresolved, step 11 BLOCK verdict, step 12 tests failing twice, step 15 commit still failing after one retry, step 16 empty list) still terminate the run — those are error/completion exits, not checkpoints.
Because --auto commits everything in the working tree at the end of each task, start from a clean working tree (no unrelated uncommitted changes). If git status is dirty at step 2 in --auto mode, stop and report to the user instead of sweeping those changes into a task commit.
No discretionary pauses in --auto. The hard stops listed above are the only valid reasons to stop or ask the user something mid-run. Do not invent additional checkpoints — do not pause to offer a commit, confirm direction, summarize progress, checkpoint a subsystem boundary, or ask whether to proceed between tasks. If a general instruction elsewhere (e.g., "only commit when the user asks" or "confirm risky actions") seems to conflict with --auto, resolve it by not performing the action, not by pausing. The user authorized an unattended sweep by passing --auto; interrupting that sweep for any reason outside the hard-stop list violates the contract.
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.
- 2mo ago First seen · 347 lines · 0 tokens per session scan A 1f109cb04c6d
work is a skill published in the GitHub repository michaelcjoseph/agent-coding-setup (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,063 tokens. 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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…