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/impactcrew/dont-be-a-sloperator/worknpx skills add impactcrew/dont-be-a-sloperator --skill workgit clone --depth 1 https://github.com/impactcrew/dont-be-a-sloperatorWrote 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/impactcrew/dont-be-a-sloperator/work)<a href="https://agentmods.dev/skills/impactcrew/dont-be-a-sloperator/work"><img src="https://agentmods.dev/badge/skills/impactcrew/dont-be-a-sloperator/work.svg" alt="Measured on agentmods" 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 | $0.00027 | $0.02142 |
| Opus 5 | $0.00014 | $0.01071 |
| Sonnet 5 | $0.00005 | $0.00428 |
| Haiku 4.5 | $0.00003 | $0.00214 |
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 4d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/work - Structured Task Intake
You are starting a new task. Follow the Workflow Protocol phases strictly. Do NOT skip to output.
Iron Laws are active. Read and follow ALL Iron Laws from ~/.claude/CLAUDE.md. Tag every action with the governing law using [Law #N] inline notation. Apply the Critical Thinking checkpoint (Law #2) at every phase gate. No exceptions.
First: Determine the task type
Read the user's task description and classify:
- Code task: Writing, modifying, or debugging code, configuration, or infrastructure
- Content task: Writing, editing, researching, planning, or any non-code deliverable
This determines which steps apply within each phase. The four phases themselves always run in order.
Agent-first approach [Law #9] (code tasks only): For code tasks, your default mode is delegation, not serial execution. Maximum 3 concurrent agents (more kills performance). If you have more than 3 independent tasks, batch them in waves of 3. For content tasks, agents are rarely useful since the work is inherently sequential and voice/tone must stay consistent.
What the user said
The user's message after /work is the task description. If no description was provided, ask what they want to do.
Step 1: UNDERSTAND (Phase 1)
Read everything relevant before forming any opinions.
For code tasks:
Launch an Explore agent unless the affected area is fewer than 5 files that you can already identify by name:
- Read the project's CLAUDE.md yourself (this is fast and needed for coordination)
- Launch an
Exploreagent (subagent_type: "Explore") via the Agent tool to map the affected codebase areas - If the task spans multiple distinct areas, launch separate Explore agents in parallel
- If you skip the Explore agent, state why: "Skipping Explore agent: affected files are [list them]."
For content tasks:
- Read any source material the user provided or referenced
- Research the topic if needed (web search, reading existing docs)
- Understand the context: what already exists, what this builds on, what it replaces
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.
- 4d ago First seen · 220 lines · 27 tokens per session scan A 54420ae445f3
work is a skill published in the GitHub repository impactcrew/dont-be-a-sloperator (10 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 2,142 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…