Borrowing it
Nothing to install: this file belongs to auerbachb/claude-code-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/auerbachb/claude-code-config/main/.claude/skills/standup/SKILL.mdgit clone --depth 1 https://github.com/auerbachb/claude-code-configWrote 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/auerbachb/claude-code-config/standup)<a href="https://agentmods.dev/skills/auerbachb/claude-code-config/standup"><img src="https://agentmods.dev/badge/skills/auerbachb/claude-code-config/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/auerbachb/claude-code-config/standup"><img src="https://agentmods.dev/badge/skills/auerbachb/claude-code-config/standup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 9 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.
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.00035 | $0.02838 |
| Opus 5.5 | $0.00014 | $0.01135 |
| Sonnet 5.5 | $0.00007 | $0.00568 |
| Haiku 4.5 | $0.00003 | $0.00284 |
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 1mo 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate a standup report summarizing what was accomplished since $ARGUMENTS (default: smart lookback to previous workday noon ET — skips weekends and US federal holidays).
How to gather data
Step 1: Find repos and set time range
-
Find all repos the user works in. Check recent git activity across known repo paths. Start with the current working directory, then check other repos mentioned in conversation context or memory.
-
Determine the lookback cutoff. If the user provided an explicit
$ARGUMENTStime reference, use it directly (skip to the ISO conversion below). If no argument was given, compute the smart default: find the most recent prior workday by walking backwards from yesterday, skipping weekends, US federal holidays, and the day after Thanksgiving (a de facto holiday for most organizations).Smart lookback algorithm (run only when
$ARGUMENTSis empty):# Delegates to workday.sh, which implements the full weekend + # US-federal-holiday + day-after-Thanksgiving calculator with observed-date # rules (Sat → Fri, Sun → Mon) and cross-year lookbacks. # # Resolve the script path robustly: /standup runs from arbitrary repos, # so a bare `.claude/scripts/workday.sh` only works when CWD happens to be # this config repo. Check in this order: skills-worktree (canonical), # ~/.claude/scripts (global symlink fallback), git root of the current repo, # then CWD-relative. # Capture GIT_ROOT first and only include that candidate when non-empty — # otherwise `$(git rev-parse …)` expands to "" and the candidate becomes # `/.claude/scripts/workday.sh` (absolute-root path), which would # incorrectly match an unrelated root-level file if one existed. WORKDAY_SH="" GIT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || true) for candidate in \ "$HOME/.claude/skills-worktree/.claude/scripts/workday.sh" \ "$HOME/.claude/scripts/workday.sh" \ "${GIT_ROOT:+$GIT_ROOT/.claude/scripts/workday.sh}" \ ".claude/scripts/workday.sh"; do [ -n "$candidate" ] || continue if [ -x "$candidate" ]; then WORKDAY_SH="$candidate" break fi done if [ -z "$WORKDAY_SH" ]; then echo "Error: could not locate workday.sh" >&2 exit 1 fi # Preserve workday.sh's exit-code contract (exit 3 = runtime failure). # A plain `LOOKBACK_DATE=$(...)` would swallow non-zero exits and later # collapse them to a generic `exit 1`; `|| exit $?` keeps the original. LOOKBACK_DATE=$("$WORKDAY_SH" --last-workday) || exit $? # LOOKBACK_DATE is now the most recent prior workday (YYYY-MM-DD)
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.
- 1mo ago Changed 9e1ad6803a06
- 2mo ago First seen · 203 lines · 35 tokens per session scan A 1861fe434d12
standup is a skill published in the GitHub repository auerbachb/claude-code-config (5 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 2,838 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-31.
Other skills, from other repositories
jira
Unified Jira entry point. Routes to preview (default), create, or review subcommands.
revert
Git-aware revert that understands Draft tracks, phases, and tasks. Safely undo work at task, phase, or track level. Use when the user asks to 'revert this track', 'undo a phase', 'revert task X', or says 'roll back the last task', 'undo this work'.
standup
Generate standup summary from git history, track progress, and Jira/GitHub activity. Read-only — makes no changes to the codebase.
status
Display current progress of Draft tracks and active tasks. Shows phases, completion percentages, and blocked items.
integrations
Canonical integrations parent command. Handles external system exports and syncs. Routes intent to jira-preview or jira-create based on context.
ops
Primary router for operations, deployment, incident, and lifecycle workflows. Analyzes intent and dispatches to deploy-checklist, incident-response, standup, status, revert. Use for pre-deploy verification, handling outages, daily summaries, progress checks, and safe rollbacks.