daily-standup

daily-standup is a skill for Claude Code, Codex from pilotspace/pilot-space. It costs 16 tokens per session (874 once invoked), scanned A, original, Apache-2.0.

A workflow that creates a daily standup report from issue activity for the requesting user. A standup is a short team update covering completed work, current work, and blockers.

In plain words
What is it for?
Use it for a daily standup or when asking what you worked on yesterday. It accounts for weekends when calculating Monday's previous work period and lists blocked issues with their dependencies.
Why use it?
It saves time gathering yesterday's completed tasks and today's active work into a consistent format. It also makes dependencies and obstacles visible to the team.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it for a daily standup or when asking what you worked on yesterday. It accounts for weekends when calculating Monday's previous work period and lists blocked issues with their dependencies.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pilotspace/pilot-space/daily-standup
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 pilotspace/pilot-space --skill daily-standup
Clone the repo
git clone --depth 1 https://github.com/pilotspace/pilot-space

Made for: Claude Code, Codex.

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.

agentmods badge for daily-standup

README.md
[![agentmods](https://agentmods.dev/badge/skills/pilotspace/pilot-space/daily-standup/github.svg)](https://agentmods.dev/skills/pilotspace/pilot-space/daily-standup)
Your own site
<a href="https://agentmods.dev/skills/pilotspace/pilot-space/daily-standup"><img src="https://agentmods.dev/badge/skills/pilotspace/pilot-space/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.

agentmods 80×15 button for daily-standup

Your own site · 80×15
<a href="https://agentmods.dev/skills/pilotspace/pilot-space/daily-standup"><img src="https://agentmods.dev/badge/skills/pilotspace/pilot-space/daily-standup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 874 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.00874
Opus 5.5 $0.00006 $0.00350
Sonnet 5.5 $0.00003 $0.00175
Haiku 4.5 $0.00002 $0.00087

Measured 2mo ago against content hash 6fadcdfb751c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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.

backend/src/pilot_space/ai/templates/skills/daily-standup/SKILL.md · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Daily Standup Skill

Generate a ready-to-share standup report by querying issue states and transitions for the requesting user.

Quick Start

Use this skill when:

  • User requests standup (/daily-standup, /standup)
  • User asks "what did I work on yesterday?" or "generate my standup"
  • User needs a quick status update for a team meeting

Example:

User: /daily-standup

## Yesterday (Completed)
- [PS-42] Implement OAuth 2.0 login flow
- [PS-38] Fix pagination on issue list

## Today (In Progress)
- [PS-45] Add ghost text block-type routing
- [PS-51] Write unit tests for standup skill

## Blockers
- [PS-49] Deploy staging environment — blocked by: waiting on DevOps credentials (depends on PS-47)

Workflow

  1. Determine Workday Window

    • If today is Monday, "yesterday" covers Friday through Sunday (3 days)
    • If today is Tuesday-Friday, "yesterday" covers the previous calendar day
    • Use UTC dates for consistency; the window starts at 00:00 UTC of the first covered day
  2. Query Completed Issues (Yesterday)

    • Use list_issues with state filter Done
    • Filter to issues assigned to the requesting user
    • Filter to issues whose state transitioned to Done within the workday window
    • Include issue identifier (e.g., PS-42) and title
  3. Query In-Progress Issues (Today)

    • Use list_issues with state filter In Progress
    • Filter to issues assigned to the requesting user
    • Include issue identifier and title
  4. Query Blocked Issues (Blockers)

    • Use list_issues with state filter Blocked
    • Filter to issues assigned to the requesting user
    • For each blocked issue, use get_issue to retrieve dependency context and blocker reason
    • Include issue identifier, title, and blocking reason
  5. Format Output

    • Use the three-section format: Yesterday, Today, Blockers
    • Each item is a bullet with [PS-XX] Title
    • Blockers include a " -- blocked by: {reason}" suffix
    • If a section has no items, include "(No items)" under that heading
    • If all sections are empty, add a suggestion: "No recent activity found. Consider reviewing backlog items."

Read the full file on GitHub · 116 lines

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.

  1. 2mo ago First seen · 116 lines · 16 tokens per session scan A 6fadcdfb751c

Subscribe to this mod's changes

daily-standup is a skill published in the GitHub repository pilotspace/pilot-space (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 874 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other skills, from other repositories

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 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

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

ring:mapping-feature-relationships

Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…

LerianStudio/ring · 104 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens