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/khaledsaeed18/dotclaude/standup-summarynpx skills add KhaledSaeed18/dotclaude --skill standup-summarygit clone --depth 1 https://github.com/KhaledSaeed18/dotclaudeWrote 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/khaledsaeed18/dotclaude/standup-summary)<a href="https://agentmods.dev/skills/khaledsaeed18/dotclaude/standup-summary"><img src="https://agentmods.dev/badge/skills/khaledsaeed18/dotclaude/standup-summary.svg" alt="Measured on agentmods" 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.00082 | $0.00880 |
| Opus 5 | $0.00041 | $0.00440 |
| Sonnet 5 | $0.00016 | $0.00176 |
| Haiku 4.5 | $0.00008 | $0.00088 |
Grade A, and why
standup-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 6d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reconstruct the update from evidence, not memory. Git and the issue tracker already know what happened; the job is to translate that record into the three or four sentences a teammate actually wants to hear, at the altitude of outcomes ("shipped the retry logic for webhooks") rather than mechanics ("bumped a dependency, fixed a typo, refactored a helper").
Step 1: Establish scope
- Time window: since the last workday for a standup, the last 5-7 days for a weekly. Confirm if unstated and ambiguous.
- Identity: the git author to filter by -
git config user.name/user.emailin the current repo, unless told otherwise. - Repositories: default to the current one; ask whether other repos should be included when the user's request implies more ("what did I do this week" often spans several).
Step 2: Collect the evidence
Per repository:
# Commits by the author in the window, all branches
git log --all --author="<email-or-name>" --since="<window>" \
--pretty="%h %ad %s" --date=short
# Branches touched recently
git for-each-ref --sort=-committerdate refs/heads/ \
--format="%(committerdate:short) %(refname:short)" | head -10
When gh is available and the repo has a GitHub remote, add the PR and review picture:
gh pr list --author "@me" --state all --limit 15 \
--json number,title,state,updatedAt,isDraft
gh search prs --reviewed-by "@me" --updated ">$(date -v-7d +%Y-%m-%d)" --limit 10 2>/dev/null
gh issue list --assignee "@me" --state all --limit 15 --json number,title,state,updatedAt
Uncommitted work counts too: git status --short plus the current branch name usually reveals what is in progress right now.
Step 3: Synthesize at outcome altitude
Group raw items into narrative units - a feature, a fix, a review effort - not one bullet per commit. Fifteen commits on one branch are one line. Then sort into:
- Done: merged, shipped, closed. Lead with the user-visible or team-visible effect.
- In progress: open PRs (note if awaiting review - that is a nudge, not filler), the active branch, drafts.
- Blocked / waiting: PRs awaiting someone else, issues waiting on answers, anything the log shows stalled for days. Only include real blockers; do not invent one for symmetry.
- Next: only what the evidence supports (assigned issues, an obvious follow-up) or what the user tells you. Never fabricate plans.
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.
- 6d ago First seen · 67 lines · 82 tokens per session scan A caa2b249be7f
standup-summary is a skill published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 4d ago), licensed MIT. It adds 82 tokens to every session and 880 once invoked, about $0.0004 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
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
case-interview-practice
Interactive consulting case interview practice with structured frameworks, feedback mechanisms, and progressive difficulty. Use when preparing for management consulting interviews, case competitions, or business problem-solving exercises.
finance
Financial analysis expertise for financial modeling (DCF, LBO, M&A), valuation, financial statement analysis, capital allocation, treasury management, and corporate finance decisions. Use when building financial models, analyzing statements, or making investment decisions.
i18n-localization
Internationalization and localization for global applications. Use when adding multi-language support, handling regional formats, or preparing apps for global markets.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.
impact-report-writer
Nonprofit/NGO impact report generation with data visualization suggestions, outcome metrics, narrative structure, and program data presentation. Use when writing impact reports, annual reports, or program evaluation summaries.