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 skills add drn/dots --skill standupgit clone --depth 1 https://github.com/drn/dotsWrote 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/drn/dots/standup)<a href="https://agentmods.dev/skills/drn/dots/standup"><img src="https://agentmods.dev/badge/skills/drn/dots/standup.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.00635 |
| Opus 5 | $0.00019 | $0.00318 |
| Sonnet 5 | $0.00008 | $0.00127 |
| Haiku 4.5 | $0.00004 | $0.00064 |
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 4d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Standup
Generate a quick summary of recent work for standups or status updates.
Arguments
$ARGUMENTS- Optional:--teamto include all authors, or a custom time range (e.g., "3 days")
Context
- Current branch: !
git branch --show-current - Git user email: !
git config user.email 2>/dev/null | head -1 - Git user name: !
git config user.name 2>/dev/null | head -1 - Commits since yesterday: !
git log --all --oneline --since="yesterday" 2>/dev/null | head -30 - Open PRs: !
gh pr list --author @me --state open 2>/dev/null | head -20 - Uncommitted changes: !
git status --short 2>/dev/null | head -10 - Recent branches: !
git branch --sort=-committerdate --format='%(refname:short) %(committerdate:relative)' 2>/dev/null | head -10
Instructions
Step 1: Determine scope
- If
--teamis in$ARGUMENTS, include all authors. Otherwise filter to the current user (match against the git user email and name from context). - If a custom time range is provided, use it instead of "since yesterday".
Step 2: Gather activity
Run git log filtered to the appropriate author and time range:
git log --all --oneline --author="<email>" --since="<range>"
Also check for any PRs merged in the time range:
gh pr list --author @me --state merged --limit 10
Step 3: Format the standup
Print in this format:
## Standup — <date>
### Yesterday
- <commit summary grouped by branch/feature>
- <PRs merged>
### Today
- <inferred from current branch name and uncommitted changes>
- <open PRs that need attention>
### Open PRs
- #<number>: <title> (<status/checks>)
If there is no activity for "Yesterday", say "No commits found" rather than omitting the section.
For "Today", infer from:
- The current branch name (what feature/fix is in progress)
- Any uncommitted changes (what is being worked on now)
- Open PRs awaiting review
Step 4: Offer actions
After presenting the standup, offer to:
- Copy to clipboard (
pbcopy) - Adjust the time range and regenerate
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.
- 4d ago First seen · 77 lines · 38 tokens per session scan A 8ca156e5a796
standup is a skill published in the GitHub repository drn/dots (23 stars, last pushed 3d ago), licensed MIT. It adds 38 tokens to every session and 635 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-09-03.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.