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 standupgit 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/standup)<a href="https://agentmods.dev/skills/ryanb/dotfiles/standup"><img src="https://agentmods.dev/badge/skills/ryanb/dotfiles/standup/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/standup"><img src="https://agentmods.dev/badge/skills/ryanb/dotfiles/standup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 7 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium Rogue Agent · line 22 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 233 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00044 | $0.03117 |
| Opus 5.5 | $0.00018 | $0.01247 |
| Sonnet 5.5 | $0.00009 | $0.00623 |
| Haiku 4.5 | $0.00004 | $0.00312 |
Grade A, and why
standup 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 29d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
standup — Summarize work since last standup
Summarize work done in the user's configured repo directory since the last standup, grouped by category. The output is meant to be read aloud at a standup, so keep it concise.
Priority of the output — put the user's own work first:
- PRs the user created within the window (any state).
- Other PRs the user authored that had activity in the window (updates, new commits, state changes).
- Activity on other people's PRs (reviews, merges, comments).
- Local branches with a summary of the user's own commits (ignore commits by others).
Step 1: Load configuration
Read ~/.claude/standup.json. If the file does not exist, stop and instruct the user to create it with this shape:
{
"base_path": "~/code/your-project-root",
"default_branch": "main",
"preferences": "Optional freeform instructions applied to the output."
}
Only base_path is required. Extract the values with jq:
config=~/.claude/standup.json
base_path=$(jq -r '.base_path // empty' "$config")
default_branch=$(jq -r '.default_branch // "main"' "$config")
preferences=$(jq -r '.preferences // empty' "$config")
# Expand a leading ~ in base_path
base_path="${base_path/#\~/$HOME}"
If base_path is empty, stop with an error.
Step 2: Determine the since date
Priority:
- If
$ARGUMENTSis non-empty, use it verbatim as the since date. - Else if
~/.claude/standup-last-timestampexists, read its contents and use that as the since date. The file stores an ISO 8601 timestamp written by a previous run of this skill. - Else default to
24 hours ago.
Store the chosen value in $since. Also compute a full ISO 8601 timestamp for gh search — GitHub search accepts >=YYYY-MM-DDTHH:MM:SSZ, and we want time-of-day precision so reruns in the same day don't re-list already-reported PRs.
# If $since is already an ISO timestamp (from the last-timestamp file), normalize to UTC Z form.
# Otherwise resolve the relative phrase via BSD date.
if [[ "$since" == ????-??-??T* ]]; then
# e.g. 2026-04-13T11:11:39-0700 → 2026-04-13T18:11:39Z
since_ts=$(date -j -u -f "%Y-%m-%dT%H:%M:%S%z" "$since" +%Y-%m-%dT%H:%M:%SZ)
else
# Parse forms like "36 hours ago", "24 hours ago", "2 days ago", "yesterday",
# "last friday", "past 36 hours" — normalize to BSD `date -v` adjustments.
case "$since" in
"yesterday") adj="-1d" ;;
"last friday") adj="-fri" ;;
*"hour"*|*"hours"*) n=$(echo "$since" | grep -oE '[0-9]+'); adj="-${n}H" ;;
*"day"*|*"days"*) n=$(echo "$since" | grep -oE '[0-9]+'); adj="-${n}d" ;;
*"week"*|*"weeks"*) n=$(echo "$since" | grep -oE '[0-9]+'); adj="-${n}w" ;;
*) adj="-1d" ;; # safe default
esac
since_ts=$(date -j -u -v"$adj" +%Y-%m-%dT%H:%M:%SZ)
fi
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.
- 29d ago Changed · +1 lines c1e10e895431
- 1mo ago First seen · 240 lines · 44 tokens per session scan A 262fd23b7d7a
standup is a skill published in the GitHub repository ryanb/dotfiles (2,400 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 3,117 once invoked, about $0.0002 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
remove
Remove a deployed framework or addon from the current workspace.