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 commands/mfmezger/ai_agent_dotfiles/tidy-firstgit clone --depth 1 https://github.com/mfmezger/ai_agent_dotfilesWrote 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/mfmezger/ai_agent_dotfiles/tidy-first)<a href="https://agentmods.dev/commands/mfmezger/ai_agent_dotfiles/tidy-first"><img src="https://agentmods.dev/badge/commands/mfmezger/ai_agent_dotfiles/tidy-first.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.00081 | $0.01389 |
| Opus 5 | $0.00041 | $0.00694 |
| Sonnet 5 | $0.00016 | $0.00278 |
| Haiku 4.5 | $0.00008 | $0.00139 |
Grade A, and why
tidy-first 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 6d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tidy First
Follow Kent Beck's "Tidy First" approach by strictly separating structural changes from behavioral changes in all development work.
Source
This skill is adapted from the community skill snrsw-dotfiles-tidy-first
on the LobeHub Skills Marketplace.
- Original skill page: https://lobehub.com/skills/snrsw-dotfiles-tidy-first?activeTab=skill
- Raw SKILL.md: https://lobehub.com/skills/snrsw-dotfiles-tidy-first/skill.md
- Upstream author: @snrsw — repo: snrsw/dotfiles
- Upstream version referenced: 1.0.1
The instructional content below is the original skill's guidance, lightly
reformatted for this dotfiles repo. Marketplace install/registration steps
from the upstream page are intentionally omitted — this skill ships directly
via shared/skills/ and is synced to each tool by scripts/sync-skills.sh.
Core Principle
Separate all changes into two distinct types:
-
Structural changes — rearranging code without changing behavior:
- Renaming variables, functions, classes
- Extracting methods or functions
- Moving code to different files or modules
- Reorganizing code structure
- Improving code organization
-
Behavioral changes — adding or modifying actual functionality:
- Adding new features
- Fixing bugs
- Changing business logic
- Modifying functionality
Golden Rules
Never mix change types
- Never mix structural and behavioral changes in the same commit.
- Each commit is either purely structural OR purely behavioral.
- This makes code review easier and debugging simpler.
Structural changes first
- When both kinds of change are needed, always do the structural changes first.
- Tidy the code before adding new behavior.
- Prepare the structure to receive new functionality.
Validate structural changes
- Validate that structural changes do not alter behavior.
- Run all tests before making the structural change.
- Run all tests after making the structural change.
- Tests must pass with the same results before and after. If behavior changed, it was not a pure structural change.
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.
- 6d ago First seen · 176 lines · 81 tokens per session scan A 82f76958d310
tidy-first is a command published in the GitHub repository mfmezger/ai_agent_dotfiles (5 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 1,389 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 commands, from other repositories
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer.
opsx-bulk-apply
Apply multiple OpenSpec changes concurrently in isolated worktrees.
voiceover
Start a feature the demo-driven way — approve the voice-over (instead of a PRD), build on a fresh worktree, ship a PR with the proof on it.
release
Run the iPolloWork release flow.
release
Verify, sweep docs, cut a version — then hand the release sequence back.
wtfp:checkpoint
Save, list, or restore an exact portable paper-state checkpoint.