Borrowing it
Nothing to install: this file belongs to banshee-data/velocity.report. 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/banshee-data/velocity.report/main/.claude/skills/standup/SKILL.mdgit clone --depth 1 https://github.com/banshee-data/velocity.reportWrote 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/banshee-data/velocity.report/standup)<a href="https://agentmods.dev/skills/banshee-data/velocity.report/standup"><img src="https://agentmods.dev/badge/skills/banshee-data/velocity.report/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.
<a href="https://agentmods.dev/skills/banshee-data/velocity.report/standup"><img src="https://agentmods.dev/badge/skills/banshee-data/velocity.report/standup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00529 |
| Opus 5.5 | $0.00014 | $0.00212 |
| Sonnet 5.5 | $0.00007 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
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 1mo 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: standup
Run a daily repo standup. Surfaces worktree health, branch sync status, and today's priorities.
Usage
/standup
Procedure
1. Gather repo facts
Run the standup script if it exists:
scripts/flo-standup.sh --all-branches
If the script does not exist, gather the equivalent manually:
git worktree list
git branch -vv
git status
For each worktree: identify the branch, whether it tracks an upstream, and whether it is ahead, behind, or diverged.
2. Check sync before planning
Surface these conditions explicitly before proposing any work:
- Dirty worktrees (uncommitted changes)
- Branches behind upstream
- Branches behind
origin/main - Detached HEAD worktrees: map to the containing local/remote ref
- Duplicate or overlapping work across worktrees
Do not move to priorities until sync issues are identified.
3. Read planning context
After the snapshot:
- Read
docs/BACKLOG.md - Read only the plan docs that match the active branches or recently changed areas (do not load the full
docs/plans/directory)
4. Produce the standup
## State
- [Repo/worktree/branch snapshot]
- [Sync status against upstream and `origin/main`]
## Today
1. [Top priority]
2. [Second priority]
3. [Optional third priority]
## Risks
- [Blocker, ambiguity, or migration concern]
## Options
- Option A: [Fastest path]
- Option B: [Safer path]
- Option C: [Cleanup/refactor path]
5. Adapt to delivery mode
- Interactive session: keep the summary brief, offer options, ask at most one concrete prioritisation question
- PR/comment mode: convert into a written report with explicit next actions and owners
Notes
- This skill reads only. It does not modify any files or plans.
- Treat worktrees as first-class: include detached worktrees and call out branch ambiguity explicitly.
- If priorities are clear and there are no sync issues, keep options brief.
- Do not load all plan docs: only those relevant to active branches.
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.
- 1mo ago First seen · 92 lines · 35 tokens per session scan A 9e5a91105591
standup is a skill published in the GitHub repository banshee-data/velocity.report (11 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 529 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-09-25.
standup compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| standupbanshee-data/velocity.report | Skill | 11 | today | Apache-2.0 | A | 35 | Claude Code |
| merge-batchdiegosouzapw/OmniRoute | Skill | 83k | 5d ago | MIT | A | 46 | Claude Code |
| prowler-commitprowler-cloud/prowler | Skill | 15k | yesterday | Apache-2.0 | A | 44 | Claude Code, Codex |
| gh-auth-isolationgithub/gh-aw | Skill | 5.6k | yesterday | MIT | A | 20 | Claude Code, Codex |
| github-skillzeenie-ai/OpenCompany | Skill | 1.1k | yesterday | MIT | A | 51 | Claude Code |
| comet-githubrpamis/comet | Skill | 3.3k | yesterday | MIT | A | 72 | Claude Code, Codex |
| release-helperSahir619/fable-method | Skill | 2.3k | 1mo ago | MIT | A | 43 | Claude Code |