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 instructions/wazimmerman/zimster/agents-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/instructions/wazimmerman/zimster/agents-md)<a href="https://agentmods.dev/instructions/wazimmerman/zimster/agents-md"><img src="https://agentmods.dev/badge/instructions/wazimmerman/zimster/agents-md.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.00178 | $0.00178 |
| Opus 5 | $0.00089 | $0.00089 |
| Sonnet 5 | $0.00036 | $0.00036 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
zimster AGENTS.md 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 5d 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
Zimster contributor instructions
- Use Node 22 or newer and add no runtime dependency without measured need.
- Keep core skills harness-neutral and operating-system-neutral.
- Add or update a failing structural/behavioral test before changing policy.
- Work on a feature branch/worktree; commit at verified vertical-slice boundaries unless the user explicitly requests no commits.
- Review
git status --short,git diff,git diff --cached, and all untracked files before completion. - Preserve third-party notices for adapted material.
- Do not add mandatory agents, nested delegation, or review loops without an evaluation showing a quality gain that justifies the economics.
- Synchronize the Codex mirror after canonical plugin changes.
- Run
npm run check,npm run version:check, andgit diff --checkbefore completion.
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.
- 5d ago First seen · 16 lines · 178 tokens per session scan A 7c0b6a413eb1
zimster AGENTS.md is an instructions file published in the GitHub repository wazimmerman/zimster (2 stars, last pushed 3d ago), licensed MIT. It adds 178 tokens to every session, about $0.0009 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 instructions, from other repositories
aristo CLAUDE.md
Instructions for aretta-ai/aristo, covering claude.md — aristo working agreement, §1. commit size — small or medium only, §2. commit messages — semantic / conventional, §3. changelog.md — one line per commit, in the same commit and §4. test-first — no test, no claim of correctness.
vibe-coding-repository-standard AGENTS.md
Instructions for cz1993/vibe-coding-repository-standard, covering vcrs repository instructions, purpose, communication, change discipline and privacy and safety.
TreeWork AGENTS.md
Instructions for Johnny-xuan/TreeWork, covering treework repository guidance, read before editing, repository boundaries and change discipline.
apex-workflow AGENTS.md
AGENTS.md instructions for 0xCozart/apex-workflow, covering apex workflow agent instructions, install flow and guardrails.
thoughtweave CLAUDE.md
Instructions for Amatofrancesco99/thoughtweave, a project described as: The SDD (+TDD) workflow for coding agents that adapts to your level - teaching when new, challenging even when expert. Captures engineering best practices for any software context while ensuring quality, standardization and continuous learning.…
matt-skills-with-to-goal CLAUDE.md
Instructions for tt-a1i/matt-skills-with-to-goal: Skills are organized into bucket folders under skills/.