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 wazimmerman/zimster --skill designing-workgit clone --depth 1 https://github.com/wazimmerman/zimsterWrote 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/wazimmerman/zimster/designing-work)<a href="https://agentmods.dev/skills/wazimmerman/zimster/designing-work"><img src="https://agentmods.dev/badge/skills/wazimmerman/zimster/designing-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/wazimmerman/zimster/designing-work"><img src="https://agentmods.dev/badge/skills/wazimmerman/zimster/designing-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.00019 | $0.01153 |
| Opus 5 | $0.00010 | $0.00576 |
| Sonnet 5 | $0.00004 | $0.00231 |
| Haiku 4.5 | $0.00002 | $0.00115 |
Grade A, and why
designing-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 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designing Work
Use this skill when choices about scope, architecture, behavior, or acceptance would materially change the implementation. Skip it for exact low-risk edits.
Choose design depth from the work itself:
- exact, low-risk, well-defined work proceeds without design ceremony;
- material ambiguity or a consequential choice gets compact design;
- a large product, major architecture or UX decision, security or migration boundary, public contract, or expensive commitment gets deeper collaborative design;
- an oversized multi-system request is decomposed before one bounded workstream receives deeper design.
Do not turn this hierarchy into a universal brainstorming gate. Do not require one question per turn, a committed specification for routine work, or agents whose only purpose is brainstorming.
1. Inspect before asking
Read the repository instructions, relevant code, tests, architecture notes, and recent changes. Prefer answering questions from the project over asking the user to repeat information already present.
Identify:
- the current behavior and authoritative interfaces;
- the requested outcome;
- constraints and explicit exclusions;
- external systems, hardware, migrations, concurrency, or security risks;
- evidence that can and cannot be produced in the current environment.
Decompose only oversized requests
After inspection, decide whether the request is one complex but coherent system or multiple substantial, loosely coupled systems with independently meaningful workstreams. A request touching many files does not by itself require decomposition, and a well-scoped request should proceed normally.
When one plan would be too broad to stay coherent:
- identify logical subprojects or bounded workstreams;
- state their dependencies and recommended order;
- establish enough shared architecture and constraints to prevent incompatible subprojects;
- preserve the overall mission for later workstreams;
- select the first useful bounded piece for deeper design.
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.
- 9d ago First seen · 159 lines · 19 tokens per session scan A e2817a8ca05d
designing-work is a skill published in the GitHub repository wazimmerman/zimster (2 stars, last pushed 7d ago), licensed MIT. It adds 19 tokens to every session and 1,153 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
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.
rudder
Use locally captured coding-session intent to resolve a device-local behavioral spec, generate focused tests from that spec, implement the smallest production changes through red-green TDD, and verify coverage with the repository's native tooling. Use when the user asks to run Rudder, create or regenerate tests for…
TDD 开发纪律助手
A development skill based on TDD, or test-driven development: write or update a test first, make it pass with the smallest code change, then improve the code and check for regressions.
ship
Enforces Law 1 (Research Before Executing), Law 3 (One Thing at a Time), and Law 4 (Verify Before Reporting) of the 7 Laws of AI Agent Discipline. Fix one defect through TDD and one PR, isolate unrelated dirty checkouts in an owner-locked clean worktree, and return only eligible clean checkouts to the detected default…
debugging
Investigate failures whose root cause is still unknown — narrow the search space, instrument, and test falsifiable hypotheses. Use for intermittent or environment-dependent behavior, unexplained stack traces, regressions with no known trigger, or any symptom without a confirmed cause. Ends once the root cause is…
architecture-review
Method for assessing a codebase's structure — duplication, single-responsibility violations, layering problems, and coupling — and recommending minimal, incremental improvements. Use when asked to review architecture, assess structure or technical debt, evaluate module boundaries, or plan a refactor. Reviews the…