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 Arlenjim/claude-code-for-non-coders --skill work-disciplinegit clone --depth 1 https://github.com/Arlenjim/claude-code-for-non-codersWrote 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/arlenjim/claude-code-for-non-coders/work-discipline)<a href="https://agentmods.dev/skills/arlenjim/claude-code-for-non-coders/work-discipline"><img src="https://agentmods.dev/badge/skills/arlenjim/claude-code-for-non-coders/work-discipline/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/arlenjim/claude-code-for-non-coders/work-discipline"><img src="https://agentmods.dev/badge/skills/arlenjim/claude-code-for-non-coders/work-discipline.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.00041 | $0.01487 |
| Opus 5 | $0.00020 | $0.00744 |
| Sonnet 5 | $0.00008 | $0.00297 |
| Haiku 4.5 | $0.00004 | $0.00149 |
Grade A, and why
work-discipline 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work discipline
Apply what follows to any non-trivial task. A task is non-trivial as soon as it has more than one step, more than one possible outcome, or touches something you haven't read yet.
1. Decompose before starting
Restate the request as a verifiable goal. Before touching anything, write in one sentence what will be true when the task is done — something observable, not an intention. "Improve error handling" is not verifiable; "an invalid input produces an explicit message instead of a crash" is. If you can't write that sentence, you haven't understood the request: ask the question now, not mid-work.
Separate the known from the assumed. Explicitly list:
- what you know because you read it or observed it;
- what you assume.
Every assumption must either be verified before writing code that depends on it, or flagged as a risk. An assumption that a 10-second command could verify has no right to remain an assumption.
Write the success criteria BEFORE starting. Two or three concrete points: what observable behavior, what checks must pass, what must NOT have changed. Written after the fact, criteria always bend to what you produced — that is exactly why you write them first.
Order the steps by what they teach you. Start with the step that can invalidate the whole plan: the riskiest unknown, the dependency you're not sure of, the API whose behavior you're assuming. Discovering a wall at step 1 costs an hour; discovering it at step 8 costs the plan.
Read before you edit. Never modify a file whose relevant part you haven't read in full. Read the entry points too: who calls what you're about to change, who depends on the current behavior.
Size the plan to the task. A one-line fix doesn't deserve an eight-step plan. But even the smallest task keeps the core: a verifiable goal, reading before editing, proof before conclusion.
2. Verify before saying "done"
Your work is not done when the code is written. It is done when you have tried to prove it wrong and failed.
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 · 73 lines · 41 tokens per session scan A dede99baae0a
work-discipline is a skill published in the GitHub repository Arlenjim/claude-code-for-non-coders (10 stars, last pushed 22d ago), licensed MIT. It adds 41 tokens to every session and 1,487 once invoked, about $0.0002 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
prismstack
A routing guide and builder for Prismstack, a collection of interactive skills for work in a specific field. It helps choose the right skill and load its instructions.
domain-plan
A planning tool for designing a complete set of coding-agent skills for a specific field, including how the skills and their outputs connect.
super-guide
A hands-on guide for learning how a collection of coding-agent skills works. It teaches through the user's own skills and work rather than through abstract examples.
domain-build
A builder that creates a complete collection of coding-agent skills for a specific field from a prepared skill map. It also tracks progress and can continue an interrupted build.
skill-check
A quality-review skill for checking individual skills or an entire skill collection. It uses design questions, review dimensions, and checks for common problems.
source-convert
A translator that turns outside material into reusable coding-agent skill instructions. Sources can include repositories, prompts, videos, articles, books, procedures, codebases, or user ideas.