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.
git clone --depth 1 https://github.com/gopherguides/gopher-aiWrote 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/commands/gopherguides/gopher-ai/standup)<a href="https://agentmods.dev/commands/gopherguides/gopher-ai/standup"><img src="https://agentmods.dev/badge/commands/gopherguides/gopher-ai/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/commands/gopherguides/gopher-ai/standup"><img src="https://agentmods.dev/badge/commands/gopherguides/gopher-ai/standup.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.00008 | $0.01154 |
| Opus 5.5 | $0.00003 | $0.00462 |
| Sonnet 5.5 | $0.00002 | $0.00231 |
| Haiku 4.5 | $0.00001 | $0.00115 |
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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Current git user: !
git config user.name 2>/dev/null || echo "unknown" - Current branch: !
git branch --show-current 2>&1 || echo "unknown" - Today: !
date +%A 2>/dev/null || echo "unknown" - Recent commits (24h): !
AUTHOR=\git config user.name 2>/dev/null`; git log --author="$AUTHOR" --since="24 hours ago" --format="%h %s" --all 2>/dev/null | head -10 || echo "No commits found"`
If $ARGUMENTS is empty or not provided:
Generate a standup for the default timeframe (24 hours, or 72 hours on Mondays).
Usage: /standup [timeframe]
Examples:
/standup- Last 24 hours (72h on Mondays)/standup 48h- Last 48 hours/standup 3d- Last 3 days/standup "since monday"- Since Monday
Workflow:
- Scan git commits for your user
- Group by type (features, fixes, refactors)
- Identify in-progress work and blockers
- Generate copy-paste ready standup report
Proceed with default 24h timeframe (or 72h if today is Monday).
If $ARGUMENTS is provided:
Generate a standup summary from recent git activity using the specified timeframe.
Security Validation
Before using $ARGUMENTS in git commands, validate the timeframe format:
- Valid patterns:
[0-9]+[hdwm](e.g., "48h", "3d", "1w", "2m") - Valid patterns:
"since (monday|tuesday|wednesday|thursday|friday|saturday|sunday|yesterday)" - Reject any input containing shell metacharacters:
;,|,&,$, backticks,(,),>,<
If validation fails, display: "Invalid timeframe format. Use examples like '48h', '3d', or 'since monday'"
Configuration
- Timeframe:
$ARGUMENTS(examples: "48h", "3d", "since monday") - Author: Current git user (
git config user.name)
Steps
-
Identify Author and Timeframe
- Get the current git user:
git config user.name - Parse timeframe from
$ARGUMENTSor default to 24 hours - For Monday standups, automatically look back to Friday (72h)
- Get the current git user:
-
Gather All Git Data (Parallel)
Execute ALL these commands simultaneously in a single response:
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 · +1 lines b2174fb60b21
- 1mo ago First seen · 120 lines · 8 tokens per session scan A fe1e875dbad5
standup is a command published in the GitHub repository gopherguides/gopher-ai (21 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 1,154 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
land
Resolve and squash merge one named, currently authorized pull request.
standup
Review my git commits from the past workday and generate a standup summary.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.