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 agentmods add skills/auerbachb/claude-code-config/standupnpx skills add auerbachb/claude-code-config --skill standupgit clone --depth 1 https://github.com/auerbachb/claude-code-configWhat 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 | $0.00035 | $0.02804 |
| Opus 5 | $0.00017 | $0.01402 |
| Sonnet 5 | $0.00007 | $0.00561 |
| Haiku 4.5 | $0.00003 | $0.00280 |
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 2d 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.
- 2d 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 3d ago), licensed MIT. It adds 35 tokens to every session and 2,804 once invoked, about $0.0002 per session on Opus 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
fixer
Surgical code fixer for Bug Hunter. Implements minimal, precise fixes for verified bugs. Uses doc-lookup (Context Hub + Context7) to verify correct API usage in patches. Respects fix strategy classifications (safe-autofix vs manual-review vs larger-refactor).
referee
Final arbiter for Bug Hunter. Receives Hunter findings and Skeptic challenges, independently re-reads code, and delivers authoritative verdicts with CVSS scoring and proof-of-concept generation for security findings.
commit-security-scan
Scan code changes for security vulnerabilities using Bug Hunter-native artifacts and STRIDE context. Use whenever the user asks for PR security review, commit-diff scanning, staged-change security checks, branch-comparison security review, or pre-merge security analysis of changed code.
decompose
Decompose project or track into modules with dependency mapping. Project scope updates architecture.md and derives .ai-context.md. Track scope generates hld.md (always) and lld.md (when --lld or High-complexity module triggers it) — design-mandated artifacts that drive implement, deploy-checklist, and upload sign-off.
adr
Create and manage Architecture Decision Records. Documents significant technical decisions with context, alternatives, and consequences. Also supports evaluate (assess proposals) and design (system design) modes.
deploy-checklist
Pre-deployment verification checklist. Generates customized checklists based on tech-stack with rollback triggers. Auto-invoked by /draft:upload.