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 gszr/lunar --skill standup-updategit clone --depth 1 https://github.com/gszr/lunarWrote 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/gszr/lunar/standup-update)<a href="https://agentmods.dev/skills/gszr/lunar/standup-update"><img src="https://agentmods.dev/badge/skills/gszr/lunar/standup-update/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/skills/gszr/lunar/standup-update"><img src="https://agentmods.dev/badge/skills/gszr/lunar/standup-update.svg" alt="Reviewed on agentmods" width="80" 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.00049 | $0.00600 |
| Opus 5 | $0.00024 | $0.00300 |
| Sonnet 5 | $0.00010 | $0.00120 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
standup-update 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Standup Update
Generate a concise summary of the user's work activity using the GitHub CLI
(gh) or GitHub API.
Date ranges
Always inspect:
- The previous work period.
- Today through the current time.
For the previous work period:
- Tuesday through Friday: inspect yesterday.
- Monday: inspect Friday through Sunday so weekend work is not missed.
- Use the user's local timezone when determining date boundaries.
- Do not duplicate activity between sections.
GitHub activity can establish work already performed today, but not future plans. Do not invent or infer planned work. If the user provides plans, include them in the Today section.
Scope
- Include work repositories only.
- Infer the work GitHub organization from the current repository's remote.
- Exclude personal repositories and unrelated organizations.
- Search across the whole work organization, not only the current repository.
Activity to inspect
Find the authenticated GitHub user's:
- Authored, updated, or merged pull requests.
- Commits and meaningful updates to existing pull requests.
- Submitted pull request reviews.
- Created or meaningfully updated issues.
Confirm that the user performed the activity during the target period. Do not include an item solely because another person or automation updated it.
Use PR descriptions, commits, and changed files to understand what was accomplished rather than repeating titles without context.
Writing rules
- Produce plain text.
- Keep the update concise.
- Prioritize shipped features, fixes, designs, and other substantial work.
- Group closely related PRs into one bullet.
- Mention reviews and planning work when meaningful.
- Give minor work little detail or omit it when it adds noise.
- Do not mention personal projects.
- Do not describe the collection process.
- Put raw PR or issue links in parentheses whenever possible.
- Do not use Markdown link syntax.
- Omit empty sections unless the user asks for them.
- Do not add a blockers section unless requested.
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 · 90 lines · 49 tokens per session scan A 62f24f604765
standup-update is a skill published in the GitHub repository gszr/lunar (10 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 600 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-04.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
github-brief-intake
Use when GitHub work should enter the repository work-intake route, including an Issue, Milestone, view, or cross-repository selection.
tasks
Track a numbered list of steps to completion. Use when the user gives explicit numbered steps ("1) do X 2) do Y"), says "I need to do N things", or when a multi-step job needs a checklist. Distinct from plan (strategy): tasks tracks what's done/pending during execution.
gh-issue-management
Comprehensive management of GitHub issues, including sub-issue hierarchies. Use to create, update, close, list, search, view, comment on, and manage parent-child relationships between issues in a single skill.
gh-linking-branches-to-issues
Creates and links a development branch to an issue. Use to start implementation work.
github
Triage and orient GitHub repository, pull request, and issue work through the connected GitHub app. Use when the user asks for general GitHub help, wants PR or issue summaries, or needs repository context before choosing a more specific GitHub workflow.