ryanb/dotfiles is a collection of command-line configuration files for macOS, centered on Zsh and related tools such as Git, Ruby, Rails, and IRB. It is for developers who want to customize their terminal with commands, completions, prompts, and fuzzy-finding workflows. Its catalogue skills and plugin provide coding-agent workflows built into the same setup.
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 ryanb/dotfiles --skill bisectgit clone --depth 1 https://github.com/ryanb/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/ryanb/dotfiles/bisect)<a href="https://agentmods.dev/skills/ryanb/dotfiles/bisect"><img src="https://agentmods.dev/badge/skills/ryanb/dotfiles/bisect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ryanb/dotfiles/bisect"><img src="https://agentmods.dev/badge/skills/ryanb/dotfiles/bisect.svg" alt="Reviewed on agentmods" width="80" 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.00018 | $0.00622 |
| Opus 5.5 | $0.00007 | $0.00249 |
| Sonnet 5.5 | $0.00004 | $0.00124 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
bisect 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 24d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bisect — Find the First Bad Commit
Use git bisect to binary-search through commit history and find the first commit that introduced a failure.
Step 1: Ensure clean working tree
Check that there are no staged or unstaged changes. If there are, stop and tell the user they need a clean working tree before bisecting, since git bisect checks out older commits.
git status --porcelain
If the output is non-empty, stop and ask the user to commit or stash their changes first.
Step 2: Determine the test command
Use $ARGUMENTS to understand what the user wants to test. This should describe a command or check that fails on the current commit. Determine the exact shell command to run.
Step 3: Verify the current commit is bad
Run the test command on the current commit (HEAD). If it passes (exits 0), stop and tell the user — the current commit doesn't exhibit the failure, so there's nothing to bisect.
Step 4: Find a good commit
Start searching backwards from HEAD in steps of 10 commits to find a commit where the test passes.
git stash --include-untracked -q 2>/dev/null; true
git checkout HEAD~10 --quiet
Run the test command. If it still fails, go back another 10 commits (HEAD~10 from the current position). Repeat until either:
- A passing commit is found, or
- You've gone back 100+ commits without finding a passing one — stop and ask the user for guidance (maybe a known-good commit SHA).
Once a good commit is found, note its SHA.
Step 5: Run git bisect
Return to the original branch first, then start bisecting:
git checkout - --quiet
git bisect start
git bisect bad
git bisect good <good-commit-sha>
Git will check out a middle commit. Run the test command on it:
- If the test fails →
git bisect bad - If the test passes →
git bisect good
Repeat until git reports the first bad commit.
Step 6: Record the result and clean up
Save the first bad commit SHA and message. Then reset:
git bisect reset
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.
- 24d ago Changed · +1 lines 19844b6833b4
- 1mo ago First seen · 78 lines · 18 tokens per session scan A 294f7646c92e
bisect is a skill published in the GitHub repository ryanb/dotfiles (2,399 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 622 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
merge-pr
Merge a pull request with status checks, squash merge, and branch cleanup. Handles worktree contexts.