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 OutlineDriven/odin-gemini-cli-extension --skill tidygit clone --depth 1 https://github.com/OutlineDriven/odin-gemini-cli-extensionWrote 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/outlinedriven/odin-gemini-cli-extension/tidy)<a href="https://agentmods.dev/skills/outlinedriven/odin-gemini-cli-extension/tidy"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-gemini-cli-extension/tidy.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.00084 | $0.01066 |
| Opus 5 | $0.00042 | $0.00533 |
| Sonnet 5 | $0.00017 | $0.00213 |
| Haiku 4.5 | $0.00008 | $0.00107 |
Grade A, and why
tidy 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 4d 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.
This is a copy
100% identical to tidy — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tidy — structural-cleanup dispatcher
Compress first. Before adding complexity, reduce coupling. Before changing behavior, improve structure. This skill detects what needs tidying from context and routes to the right sibling skill. Domain procedures live in the siblings — this skill owns only scope detection, dispatch, and the output contract.
Invariants:
- Every tidy action is atomic and scoped to what is already in view.
- Tidy commits are always separate from behavior commits.
- No opportunistic sweeps beyond the declared or clearly active scope.
Scope detection
Inspect context in priority order and dispatch to the first matching domain:
| Signal | Domain | Dispatch to |
|---|---|---|
File path(s), active diff, or cargo/dune target named |
Code | cleanup-codebase skill |
memory/ directory, MEMORY.md, or memory file(s) named |
Memory | memory-clean then memory-update skills |
.outline/, /tmp scratch, *.tmp, *.bak, repomix packs |
Workspace | Inline (see below) |
git sl, commit stack, commit message(s) named |
Git | git-branchless skill + atomic-commit skill |
| Docs, comments, ADRs, READMEs, plan files named | Docs | Inline (see below) |
| User explicitly says "tidy ICM" or names an ICM topic | ICM state | Inline (see below) |
| No clear signal | — | Ask: "What are we tidying — code, memory, workspace, git, docs, or ICM?" |
Inline procedures (workspace, docs, and ICM state)
These three domains are handled inline without a dedicated sibling skill.
Workspace
- Discover scratch artifacts in scope:
fd -t f -E '.git' -E 'target' -E '_build' \ '(\.(tmp|bak|outline)|repomix-output)' . fd -t f /tmp -g '<session-prefix>-*' 2>/dev/null - Confirm each is truly scratch (not referenced by any open plan, task, or active diff).
- Remove with
rip(notrm). Report count and paths.
Docs
- Scan in-scope file(s) for: stale
TODO/FIXME(git-blame date > 6 months), comments contradicting current code, commented-out code blocks, multi-paragraph docstrings on non-API-surface functions, overclaims about external contracts. - Show the current text + proposed change for each candidate. Edit only on confirmation or for purely cosmetic fixes (whitespace, spelling).
- Overclaims: annotate with
<!-- VERIFY -->and surface to the user rather than deleting.
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.
- 4d ago First seen · 88 lines · 84 tokens per session scan A fe45e4a53c8f
tidy is a skill published in the GitHub repository OutlineDriven/odin-gemini-cli-extension (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 84 tokens to every session and 1,066 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to tidy, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
git-branchless
Enforce idiomatic git-branchless during planning and executing tasks — detached-HEAD-first work, in-memory rebase via git move, event-log recovery via git undo, deferred branch creation, speculative-merge git sync for base updates. Use when planning or executing multi-commit work, history rewrites, stack edits…
tidy
Tidy-operations dispatcher. Invoke on "tidy", "clean up", "tidy this file/memory/workspace/git/docs", or when active context (current file, diff, stack, memory directory) has structural rot to resolve before touching behavior. Detects target domain from context and routes to the sibling skill. Requires explicit target…
qa
Conversational QA mode — user reports bugs in plain language, agent clarifies minimally, files GitHub issues that survive refactors. Trigger on "QA", "QA session", or ad-hoc bug reporting without a fixed deliverable shape. Distinct from branch-scoped and PR-scoped review.
request-refactor-plan
Plan a refactor as a sequence of tiny, working commits via adversarial interview. Default output is a markdown plan at /docs/refactor-plans/ .md; pass --emit-issue to also file a GitHub issue. Trigger on structural refactors (rename, extract, move, split, dedupe) — NOT new features.
setup-gitignore
Initialize or idempotently revise the repo's .gitignore by composing gitignore.io templates, AI-tooling/IDE patterns, and confirmed noise from git status. Use when the user says "set up gitignore", "fix gitignore", or untracked files keep appearing in git status.
setup-pre-commit
Install git pre-commit hooks via the project's hook tool — Husky+lint-staged (JS), pre-commit (Python/OCaml), lefthook (Go), cargo-husky (Rust). Use when the user wants commit-time formatting, linting, type-checking, or test gates. Detects ecosystem first.