standup

A command that creates a short personal standup summary from recent coding sessions, project planning files, and available project context. A standup is a brief update on what was done, what is in progress, and what remains.

In plain words
What is it for?
Use it at the beginning of the day to review recent projects, active plans, unresolved questions, and suggested next steps.
Why use it?
It reduces the effort of reconstructing where you left off when starting work.

Command

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.

agentmods
npx agentmods add commands/bluzername/claude-code-power-stack/standup
Clone the repo
git clone --depth 1 https://github.com/bluzername/claude-code-power-stack
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 342 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00342
Opus 5 $0.00000 $0.00171
Sonnet 5 $0.00000 $0.00068
Haiku 4.5 $0.00000 $0.00034

Measured 2d ago against content hash e000fdf3720a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

commands/standup.md · 51 lines

What it actually says

/standup - Morning standup with yourself

Generate a quick personal standup summary using all Power Stack tools. Run this at the start of your day to remember where you left off.

Steps

1. Recent sessions

Run this command and read the output:

ccs ls 2

List sessions from the last 2 days. Note the projects and session names.

2. Check for active planning files

Look for planning files in the current project directory:

  • If task_plan.md exists, read it and note the current phase and remaining work
  • If progress.md exists, read the last session entry
  • If findings.md exists, scan for unresolved questions

3. Ghost context

If Ghost MCP tools are available, use ghost_project_context to load relevant context for the current project. This surfaces decisions, conventions, and gotchas Ghost has captured.

4. Generate the standup

Present a concise summary in this format:

Standup - {today's date}
========================

Yesterday:
- {project}: {what was done, from planning files or session history}
- {project}: {what was done}

In progress:
- {project}: Phase {N} of task_plan.md - {description}
- {any unresolved items from findings.md}

Suggested next:
- {most logical next step based on planning files and context}

Keep it short - 5-10 lines max. This is a quick orientation, not a report.

5. Suggest session name

If the user seems ready to start working, suggest a session name using the /rename-session convention.

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. 2d ago First seen · 51 lines · 0 tokens per session scan A e000fdf3720a

Subscribe to this mod's changes

standup is a command published in the GitHub repository bluzername/claude-code-power-stack (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 342 tokens. 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.