standup

standup is a skill for Claude Code from ryanb/dotfiles. It costs 44 tokens per session (3,117 once invoked), scanned A, original, MIT.

A stand-up summary tool for software repositories. A stand-up is a short progress update; this one collects pull requests, reviews, commits, and code changes since the previous update.

In plain words
What is it for?
Use it to prepare a spoken or written daily update across configured repositories. It can cover authored or reviewed pull requests, merges, commits, and per-repository changes.
Why use it?
It removes the need to inspect each repository and pull request manually. It puts the user's own work first and groups activity into a concise update.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; reads .claude/ paths; positional $N argument.

Good fit Use it to prepare a spoken or written daily update across configured repositories. It can cover authored or reviewed pull requests, merges, commits, and per-repository changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ryanb/dotfiles/standup
About the project

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.

ryanb/dotfiles · 2,400 stars · on GitHub

Install

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.

Any agent
npx skills add ryanb/dotfiles --skill standup
Clone the repo
git clone --depth 1 https://github.com/ryanb/dotfiles

Made for: Claude Code.

Its marketplace also offers this one on its own, as the plugin standup — /plugin install standup after adding the marketplace above.

Wrote 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.

agentmods badge for standup

README.md
[![agentmods](https://agentmods.dev/badge/skills/ryanb/dotfiles/standup/github.svg)](https://agentmods.dev/skills/ryanb/dotfiles/standup)
Your own site
<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.

agentmods 80×15 button for standup

Your own site · 80×15
<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>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,117 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
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.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 29d ago against content hash c1e10e895431, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

The scan reads SKILL.md. This mod also ships 1 executable file (find-repos.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

claude/skills/standup/SKILL.md · 241 lines

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:

  1. PRs the user created within the window (any state).
  2. Other PRs the user authored that had activity in the window (updates, new commits, state changes).
  3. Activity on other people's PRs (reviews, merges, comments).
  4. 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:

  1. If $ARGUMENTS is non-empty, use it verbatim as the since date.
  2. Else if ~/.claude/standup-last-timestamp exists, 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.
  3. 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

Read the full file on GitHub · 241 lines

Files

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.

Changes

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.

  1. 29d ago Changed · +1 lines c1e10e895431
  2. 1mo ago First seen · 240 lines · 44 tokens per session scan A 262fd23b7d7a

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories