Borrowing it
Nothing to install: this file belongs to luanmorenommaciel/agentspec. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/luanmorenommaciel/agentspec/main/.claude/skills/standup-report/SKILL.mdgit clone --depth 1 https://github.com/luanmorenommaciel/agentspecWrote 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/luanmorenommaciel/agentspec/standup-report)<a href="https://agentmods.dev/skills/luanmorenommaciel/agentspec/standup-report"><img src="https://agentmods.dev/badge/skills/luanmorenommaciel/agentspec/standup-report/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/luanmorenommaciel/agentspec/standup-report"><img src="https://agentmods.dev/badge/skills/luanmorenommaciel/agentspec/standup-report.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.00114 | $0.02025 |
| Opus 5 | $0.00057 | $0.01012 |
| Sonnet 5 | $0.00023 | $0.00405 |
| Haiku 4.5 | $0.00011 | $0.00202 |
Grade A, and why
standup-report 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 7d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Standup Report
Generate the user's daily standup message: what moved forward, what comes next, and what is blocked. Assemble evidence from the repository and the user's own account, draft the three-section message, confirm it with the user, and deliver it ready to paste into the team's chat tool (Slack, Teams, or whatever the team uses).
A standup is a pulse, not a report. The format is lightweight — a greeting and emoji markers are fine — but the substance stays concrete, verifiable, and honest.
When to use
- The user asks for a standup, check-in, daily update, or the day's status message.
- The user wants yesterday's work and today's plan summarized for the team chat.
Skip if
- The input is a meeting transcript or the user wants a meeting summarized — use
meeting-analysisinstead. - The user needs a status update longer than a standup (weekly summary, retrospective, project report) — write those as documents, not chat messages.
Message template
<optional greeting line — e.g. "Good morning, team! Daily check-in:" — with the team @-mention if the user wants one>
🟢 **Done**
- <concrete verb + artifact, one line — e.g. "Merged PR #118 — retry handling in the sync client">
- <2–4 bullets per section>
🟡 **Will do**
- <next meaningful deliverable, one line — e.g. "Open the follow-up PR wiring retries into the batch endpoint">
🔴 **Blockers**
- <what is blocked + what is needed + from whom (by role), one line — or exactly "No blockers today.">
Example, filled:
Good morning, team! Daily check-in:
🟢 **Done**
- Merged PR #118 — retry handling in the sync client
- Opened PR #123 — pagination for the export endpoint
- Published the draft rollout plan for team review
🟡 **Will do**
- Start the auth-module migration once PR #123 lands
- Turn rollout-plan feedback into the final checklist
🔴 **Blockers**
- PR #123 (pagination for the export endpoint) awaits reviewer feedback — blocks the migration start
Formatting rules
- One line per bullet. Never hard-wrap inside a bullet — chat tools soft-wrap, and a hard-wrapped bullet renders as broken fragments.
- 2–4 bullets per section. More than that is a report, not a pulse — move the overflow to the thread or cut it.
- Blank line between sections — the message breathes better.
- The 🟢/🟡/🔴 markers and bold section headers are the format's identity — keep them. If the team's chat tool renders emoji shortcodes more reliably than literal emoji, swap them at delivery time.
- Team @-mention is optional and never assumed. If the user wants one, ask for the exact group handle — do not invent or guess it.
- Greeting matches the time of day, and is optional.
- Inline links where the chat renders markdown: a labeled link to a PR or issue beats a raw URL. In Blockers, make the link label descriptive enough that the reader grasps what is blocked without clicking.
- Joint work reads in the plural, solo work in the singular. "We aligned on the rollout plan" credits the team; "I opened the PR" owns the work. Do not claim shared work as solo, and do not dilute solo work into "we".
- No blockers? Say so explicitly ("No blockers today.") — never invent one to fill the section.
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.
- 7d ago First seen · 137 lines · 114 tokens per session scan A 1354a4ff7d7c
standup-report is a skill published in the GitHub repository luanmorenommaciel/agentspec (246 stars, last pushed today), licensed MIT. It adds 114 tokens to every session and 2,025 once invoked, about $0.0006 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-01.
Other skills, from other repositories
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Otto to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
gsd-ns-manage
Route to the appropriate management skill based on the user's intent. gsd-config (settings + advanced + integrations + profile) and gsd-workspace (new + list + remove) are post-#2790 consolidated entries.
slack-tools
Slack workspace management and automation specialist.
triage-inbox
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…
ceo-setup
One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a commitments project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…