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 martinemde/dotfiles --skill checkoutgit clone --depth 1 https://github.com/martinemde/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/skills/martinemde/dotfiles/checkout)<a href="https://agentmods.dev/skills/martinemde/dotfiles/checkout"><img src="https://agentmods.dev/badge/skills/martinemde/dotfiles/checkout.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00836 |
| Opus 5 | $0.00000 | $0.00418 |
| Sonnet 5 | $0.00000 | $0.00167 |
| Haiku 4.5 | $0.00000 | $0.00084 |
Grade A, and why
checkout 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Checkout: Start a New Change for an Issue
Arguments
$ARGUMENTS
Pre-computed Context
Working copy: !`jj log -r @ --no-graph -T 'change_id.shortest() ++ " " ++ if(description, description.first_line(), "(no description)")' 2>/dev/null`
Working copy empty: !`jj diff --stat 2>/dev/null | head -1`
Log: !`jj log -r 'ancestors(@, 5)' --no-graph -T 'change_id.shortest() ++ " " ++ bookmarks ++ " " ++ if(description, description.first_line(), "(empty)") ++ "\n"' 2>/dev/null`
Constraints
- Do not abandon changes or discard work without user confirmation.
Instructions
1. Parse Arguments
Determine what $ARGUMENTS contains:
| Pattern | Action |
|---|---|
#123 or issue URL |
Fetch issue title, derive bookmark name |
Bookmark name (e.g., feat/dark-mode) |
Use directly |
| Empty | Ask what to work on |
2. Derive Bookmark Name (from issue)
If $ARGUMENTS is an issue reference:
- Fetch:
gh issue view <number> --json number,title,labels - Derive bookmark name from issue metadata:
- Check labels for conventional commit type hints (bug/fix labels →
fix/, feature labels →feat/, chore/maintenance labels →chore/, default →feat/) - Format:
<prefix><number>-<kebab-case-title>(e.g.,feat/123-add-dark-mode) - Truncate to 60 characters max
- Check labels for conventional commit type hints (bug/fix labels →
3. Handle Existing Work
Check pre-computed context for the current working copy state.
In jj, the working copy @ is always a change being edited. Before starting new work, assess:
| Situation | Action |
|---|---|
| Working copy is empty (no diff) | Safe to proceed — jj new will leave an empty change behind (auto-abandoned) |
| Working copy has changes with a description | Suggest jj commit first to finalize, then proceed |
| Working copy has changes without a description | Suggest jj commit -m "..." or jj describe -m "..." first |
Conflicts exist (jj st shows conflicts) |
Inform user and wait for guidance |
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.
- 7d ago First seen · 97 lines · 0 tokens per session scan A 2bcc1f11fde7
checkout is a skill published in the GitHub repository martinemde/dotfiles (9 stars, last pushed 7d ago), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 836 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 skills, from other repositories
repo-activity
Scan all git repositories under /repos and report recent activity — last commit age, branch, uncommitted changes — in age-bucketed tables. Use when the user asks for a repo activity overview, "what have I been working on", portfolio status, or which repos are active/dormant.
github-repository
Configure a GitHub repository's description, homepage, topics, and solo-developer settings via gh, derived from the codebase. Use when tidying repo settings.
resolve-conflicts
Resolve git merge or rebase conflicts by reading both sides, keeping the intent of each change, then continuing and re-running the gate. Use when a merge or rebase conflicts.
lefthook
Canonical lefthook git-hooks setup: pre-commit (format, check, secret scan) and pre-push (test), each delegating to mise run tasks. Use for git hook configuration.
merge-ready
Drive an existing pull request to a mergeable state: get CI green, resolve merge conflicts with the base branch, address and resolve review comments, trigger required bot reviews/approvals (e.g. commenting '@claude review'), link associated issues, and clean up the PR title and description. Ends with a readiness…
conventional-commit
Write a Conventional Commits subject for the staged changes and commit them. Use when committing staged work with a typed, scoped message.