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 agentmods add commands/bluzername/claude-code-power-stack/standupgit clone --depth 1 https://github.com/bluzername/claude-code-power-stackWhat 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 | $0.00000 | $0.00342 |
| Opus 5 | $0.00000 | $0.00171 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
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.
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.mdexists, read it and note the current phase and remaining work - If
progress.mdexists, read the last session entry - If
findings.mdexists, 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.
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.
- 2d ago First seen · 51 lines · 0 tokens per session scan A e000fdf3720a
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.
Other commands, from other repositories
release
Release a new version: bump version, update changelog, tag, push, and create a GitHub release.
benchmark
Run a TAU-bench evaluation end-to-end and present results.
checkout-branch
Switch to an existing branch by checking out its worktree, or creating one if needed.
kayba-agent-instructions
The kayba CLI interacts with the Kayba hosted API (https://use.kayba.ai). Auth: set KAYBAAPIKEY env var or pass --api-key to every command.
create-branch
Create a new git branch with an associated worktree following the project naming convention.
create-pr
Create a pull request for the current branch against main.