Borrowing it
Nothing to install: this file belongs to wazimmerman/zimster. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/wazimmerman/zimster/main/.cursor/commands/using-zimster.mdgit 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/commands/wazimmerman/zimster/using-zimster)<a href="https://agentmods.dev/commands/wazimmerman/zimster/using-zimster"><img src="https://agentmods.dev/badge/commands/wazimmerman/zimster/using-zimster.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.1 | $0.00000 | $0.00173 |
| Opus 5 | $0.00000 | $0.00086 |
| Sonnet 5 | $0.00000 | $0.00035 |
| Haiku 4.5 | $0.00000 | $0.00017 |
Grade A, and why
using-zimster 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 7d 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.
What it actually says
Use the using-zimster Agent Skill for this task. Read its complete SKILL.md
before acting, select and report the risk profile, and follow its proof-first
workflow.
Decide delegation usefulness before model routing. Inherit the current model by default; use an explicitly generated custom-agent override only when this Cursor version reports compatible model fields, and report effective routing as unverified when the host does not expose it.
If the skill is not discoverable in this repository, refresh the repository skills from a Zimster checkout or extracted package:
npm run sync-skills -- --target /path/to/this/repository
Treat a missing skill after synchronization as an installation error. Expected missing harness capabilities use the quiet fallback recorded by the skill; use the Zimster doctor command when detailed diagnostics are wanted.
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.
- 7d ago First seen · 18 lines · 0 tokens per session scan A 0b83debf7773
using-zimster is a command published in the GitHub repository wazimmerman/zimster (2 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 173 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 commands, from other repositories
quick-change
PitWay: Bounded small-fix workflow, usable whenever no milestone is active.
milestone-review
PitWay: Role-based milestone review workflow (start/brief/record/report/decide).
backlog
PitWay: Capture out-of-scope work discovered mid-task, without expanding current scope.
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.
verify
PitWay: Run approved command checks, or record a manual/review result.
milestone-cancel
PitWay: Permanently abandon a draft milestone; the id is never reused.