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 rebase-stackgit 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/rebase-stack)<a href="https://agentmods.dev/skills/ryanb/dotfiles/rebase-stack"><img src="https://agentmods.dev/badge/skills/ryanb/dotfiles/rebase-stack/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/rebase-stack"><img src="https://agentmods.dev/badge/skills/ryanb/dotfiles/rebase-stack.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.05932 |
| Opus 5.5 | $0.00000 | $0.02373 |
| Sonnet 5.5 | $0.00000 | $0.01186 |
| Haiku 4.5 | $0.00000 | $0.00593 |
Grade A, and why
rebase-stack 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 yesterday.
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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rebase Stack
Rebase a chain of dependent branches in order. The first branch is rebased onto the base branch; each subsequent branch is rebased onto the previous (now-rebased) branch, keeping only that branch's own commits so nothing is duplicated.
The list you pass defines the target order and does not have to match the current chain — reordering is supported. Each branch's exclusion boundary is derived from where it actually forked, so moving a branch up or down the stack replays only its own commits. See Reordering for the extra steps a reorder needs.
Two shell scripts shipped with this skill do the mechanical work: rebase-stack.sh rewrites the local branches, and relink-stack.sh reconciles the GitHub stack and PR bases afterwards when the order changed. This skill calls them and, when the rebase pauses on a conflict, delegates the resolution to a sub-agent so the main context stays small.
Step 1: Determine the stack
Get the ordered branch list from $ARGUMENTS. The first branch is the bottom of the stack (closest to the base branch); each subsequent branch builds on the previous one. This is the target order — if it differs from the current chain, that's a reorder and the run will rewrite the stack's shape.
If no branches are supplied in $ARGUMENTS, infer the stack from the current branch.
Base branch
Determine the base branch in this order:
- Use
--base <branch>if the user specifies one (it goes before the branch list) - Use the bottom branch's tracked parent from
git config branch.<bottom>.parent, if set, still resolving to a commit, and not itself one of the stack branches - Use
bin/base-branchif the script exists and is executable - Ask the user which branch the stack sits on
Pass the result to both scripts as --base <branch> so they don't have to re-derive it.
Preferred: ask gh stack
The repo may already track the chain as a GitHub stack (the gh stack extension). Ask it first:
What ships with it
3 files 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.
- yesterday Changed · +6 lines 37796e67b5c2
- 24d ago First seen · 271 lines · 0 tokens per session scan A ee6f7a4f9d20
rebase-stack is a skill published in the GitHub repository ryanb/dotfiles (2,399 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,932 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-09-22.
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.