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/weekly-summary)<a href="https://agentmods.dev/commands/gopherguides/gopher-ai/weekly-summary"><img src="https://agentmods.dev/badge/commands/gopherguides/gopher-ai/weekly-summary/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/weekly-summary"><img src="https://agentmods.dev/badge/commands/gopherguides/gopher-ai/weekly-summary.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.00007 | $0.01151 |
| Opus 5.5 | $0.00003 | $0.00460 |
| Sonnet 5.5 | $0.00001 | $0.00230 |
| Haiku 4.5 | $0.00001 | $0.00115 |
Grade A, and why
weekly-summary 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 — 171 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" - This week's commits: !
AUTHOR=\git config user.name 2>/dev/null`; git log --author="$AUTHOR" --since="last monday" --format="%h %s" --all 2>/dev/null | head -15 || echo "No commits found"` - Week start: !
date -v-monday +%Y-%m-%d 2>/dev/null || date -d "last monday" +%Y-%m-%d 2>/dev/null || echo "Monday"
If $ARGUMENTS is empty or not provided:
Generate a summary of this week's git activity.
Usage: /weekly-summary [weeks-back]
Examples:
/weekly-summary- Current week (since Monday)/weekly-summary 1- Last week/weekly-summary 2- Two weeks ago
Workflow:
- Gather commits from the specified week
- Aggregate PRs merged and reviewed
- Calculate productivity metrics
- Group accomplishments by project/area
- Generate status report format
Proceed with current week's summary.
If $ARGUMENTS is provided:
Generate a weekly work summary for the specified week.
Configuration
- Weeks Back:
$ARGUMENTS(0 = current week, 1 = last week, etc.) - Author: Current git user (
git config user.name)
Steps
-
Calculate Date Range
# Get start of week (Monday) # For current week: this Monday # For weeks back: subtract 7*N days from this Monday git log --since="2024-01-15" --until="2024-01-22" --author="<user>" -
Gather Commits Across Repos (Parallel)
If in a multi-repo directory, execute all repo queries simultaneously:
# First, find all repos repos=$(find . -name ".git" -type d -exec dirname {} \;)Then for EACH repo, run these commands in parallel:
git logfor commitsgit shortlogfor summary- Check for merged PRs
For each repo, collect:
- Commit count
- Lines changed (additions/deletions)
- Commit messages
-
Categorize Work
Group commits by:
- Features:
feat:commits or new functionality - Bug Fixes:
fix:commits or corrections - Maintenance:
chore:,refactor:,docs:,test: - Reviews: If detectable from merge commits
- Features:
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 99f4956b8412
- 1mo ago First seen · 171 lines · 7 tokens per session scan A 8367bc516ce9
weekly-summary is a command published in the GitHub repository gopherguides/gopher-ai (21 stars, last pushed today), licensed MIT. It adds 7 tokens to every session and 1,151 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
gsd:quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
standup
Review my git commits from the past workday and generate a standup summary.
gsd:remove-phase
Remove a future phase from roadmap and renumber subsequent phases.
company-repo
Gestionar el repositorio Company Savia: crear, conectar, estado, sincronizar. El repositorio compartido de la empresa para conocimiento, mensajería y estado.
iterate
Execute a single Ralph loop iteration - complete one work unit from tasks.md with proper commits and progress tracking.
afp
Prioritise feature - assigns ID, moves to backlog (shortcut for feature-prioritise).