What is daily-standup?

A workflow for preparing and posting a daily standup report, which is a short update on completed, active, blocked, and upcoming work. It gathers information from project state, tasks, team messages, and agent availability.

Use it to review active projects, classify tasks, check the team inbox and availability, compose a dated standup summary, and post it to a chosen channel.

It collects the day's relevant information before writing the report, reducing manual status gathering. It also surfaces unread messages and blockers that may need attention.

daily-standup — Skill for Claude Code by cookjohn

Install

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.

Any agent

npx skills add cookjohn/teammcp --skill daily-standup

Clone the repo

git clone --depth 1 https://github.com/cookjohn/teammcp

Made for: Claude Code.

Or install fakechat, the plugin that ships this one along with the rest of its 9 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/cookjohn/teammcp/daily-standup/github.svg)](https://agentmods.dev/skills/cookjohn/teammcp/daily-standup)

Your own site

<a href="https://agentmods.dev/skills/cookjohn/teammcp/daily-standup"><img src="https://agentmods.dev/badge/skills/cookjohn/teammcp/daily-standup/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/cookjohn/teammcp/daily-standup"><img src="https://agentmods.dev/badge/skills/cookjohn/teammcp/daily-standup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 492 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00035	$0.00492
Opus 5	$0.00017	$0.00246
Sonnet 5	$0.00007	$0.00098
Haiku 4.5	$0.00003	$0.00049

Measured 9d ago against content hash ec17e4e26c8e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

daily-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 9d 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.

plugin-dist/templates/skills/daily-standup/SKILL.md · 63 lines

What it actually says

Daily Standup Report

Instructions

Gather project status
- Call get_state for each active project to collect current status fields.
- Note any state changes since last standup (look for fields like status, progress, blockers).
Check task board
- Call list_tasks to retrieve all tasks.
- Categorize tasks into:
  - Completed (since last standup)
  - In Progress — currently being worked on
  - Blocked — tasks with blockers
  - Pending — not yet started but assigned
Check inbox
- Call get_inbox to see any unread messages.
- Note unread count and any messages that indicate blockers or urgent requests.
Check team availability
- Call get_agents to see who is online/active.

Compose standup report

Format the report as:

Daily Standup — [today's date]

Done (since last standup):
- [completed items]

In Progress:
- [current work items with status]

Blocked:
- [blockers and what's needed to unblock]

Upcoming:
- [next priorities]

Notes:
- [unread message count, team availability, other observations]

Post the report
- Determine the target channel:
  - If $ARGUMENTS specifies a channel, use that.
  - Otherwise, default to general.
- Call send_message to post the standup report to the channel.

$ARGUMENTS

/daily-standup — Post standup to #general
/daily-standup <channel> — Post standup to the specified channel

Changes

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.

9d ago First seen · 63 lines · 35 tokens per session scan A ec17e4e26c8e

Subscribe to this mod's changes

daily-standup is a skill published in the GitHub repository cookjohn/teammcp (53 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 492 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-08-30.

Project management

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens