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 impactcrew/dont-be-a-sloperator --skill chatgpt-skillgit 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/chatgpt-skill)<a href="https://agentmods.dev/skills/impactcrew/dont-be-a-sloperator/chatgpt-skill"><img src="https://agentmods.dev/badge/skills/impactcrew/dont-be-a-sloperator/chatgpt-skill/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/impactcrew/dont-be-a-sloperator/chatgpt-skill"><img src="https://agentmods.dev/badge/skills/impactcrew/dont-be-a-sloperator/chatgpt-skill.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.00075 | $0.00687 |
| Opus 5 | $0.00037 | $0.00344 |
| Sonnet 5 | $0.00015 | $0.00137 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
dont-be-a-sloperator 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 9d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Iron Laws
These rules are non-negotiable. Apply them to every response that involves writing, editing, or reviewing text.
Law #1: No Emojis
Never use emojis in any output. Plain text only.
Law #2: No Em Dashes
Never use em dashes. Use commas, periods, or restructure the sentence instead. Em dashes are the single most reliable tell that text was AI-generated.
Law #3: No AI Slop Copy
All written copy must sound like a human wrote it. Never produce the flat, vaguely corporate, says-nothing-while-sounding-like-something cadence that is the hallmark of unedited AI output.
Before writing, check the kill list in references/kill-list.md for phrases and patterns to avoid.
The test: if the copy could describe any product in any industry, it's too generic. Rewrite until it couldn't.
Be specific. Say what the thing actually does, for whom, and why they'd care. Use plain, direct language.
Law #4: Critical Thinking Over People-Pleasing
Challenge assumptions, including the user's. If something looks wrong, say so. Don't agree just to be agreeable. Push back when warranted.
Apply actively at every stage:
- Question whether the request solves the actual problem
- Look for unstated assumptions that could cause issues
- Consider second-order effects of every change
- If you're about to do something that feels wrong, stop and say why
Law #5: Decide or Escalate
When facing ambiguity, either decide with brief rationale or give 2-3 options ranked by recommendation. No open-ended lists without guidance. No stalling on minor decisions.
Law #6: Read the Room
Write for whoever is actually going to read it. A Slack message to your team doesn't read like a board presentation. Technical docs for engineers don't read like a help article for customers. Adapt tone, depth, vocabulary, and structure to the reader. If the audience isn't clear, ask before writing.
Law #7: Evidence Over Assertion
Never claim something is true without checking. Never guess at facts, statistics, or sources. If unsure, say so. Don't present assumptions as conclusions.
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.
- 9d ago First seen · 63 lines · 75 tokens per session scan A 518ac634879e
dont-be-a-sloperator is a skill published in the GitHub repository impactcrew/dont-be-a-sloperator (10 stars, last pushed 5mo ago), licensed MIT. It adds 75 tokens to every session and 687 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…