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 skills add rockscy/solo-skills --skill standup-sologit clone --depth 1 https://github.com/rockscy/solo-skillsWrote 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/rockscy/solo-skills/standup-solo)<a href="https://agentmods.dev/skills/rockscy/solo-skills/standup-solo"><img src="https://agentmods.dev/badge/skills/rockscy/solo-skills/standup-solo/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/rockscy/solo-skills/standup-solo"><img src="https://agentmods.dev/badge/skills/rockscy/solo-skills/standup-solo.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.00066 | $0.01223 |
| Opus 5 | $0.00033 | $0.00611 |
| Sonnet 5 | $0.00013 | $0.00245 |
| Haiku 4.5 | $0.00007 | $0.00122 |
Grade A, and why
standup-solo 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 11d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Standup Solo / 单兵每日站会
When to use
- The user is a solo operator (no team to standup with).
- They want 5 minutes of forced reflection, not a project management session.
- They have access to whatever notes / commits / messages they made yesterday.
When NOT to use
- The user wants a multi-day retrospective — that's postmortem-solo.
- They want to plan a sprint — too granular, use a planning skill instead.
- They are clearly burned out — pushing them through standup theater is harmful. Suggest rest.
The three questions
A solo standup is three questions, hard limits:
- What did I actually finish yesterday? (Past, concrete, observable. "Worked on X" doesn't count — what was done?)
- What's blocked or about to block me? (Anything where the next step depends on someone or something outside my control.)
- What is the one most important thing today? (Singular. Force the user to commit.)
Output format
## Standup — YYYY-MM-DD
**Yesterday (shipped):**
- <thing 1>
- <thing 2>
**Yesterday (started but not finished):**
- <thing> — <why not done>
**Blocked:**
- <thing> — <waiting on what / who>
**Today's #1:**
> <one sentence, action-form>
**Today's #2 and #3 (only if #1 finishes):**
- <thing>
- <thing>
Inputs the user can provide
To make output sharp, the user can paste any of:
- Yesterday's git log:
git log --since="yesterday" --author=<me> --oneline - Sent emails / Slack DMs from yesterday
- A screenshot of yesterday's todo app
- Just a stream-of-consciousness brain dump
If the dev gives nothing, ask one question only: "What did you work on yesterday — give me 3 bullets, ugly is fine."
Worked example
Input (raw):
"yesterday i fixed a bug in the auth flow, started on the new pricing page but it's like 60% done, also replied to like 8 customer emails. today i need to finish pricing page and figure out why stripe webhooks are firing twice."
Output:
## Standup — 2026-04-30
**Yesterday (shipped):**
- Fixed bug in auth flow.
- Replied to 8 customer support emails.
**Yesterday (started but not finished):**
- New pricing page — ~60% done; carry over to today.
**Blocked:**
- (none reported)
**Today's #1:**
> Ship pricing page to production (the remaining 40% — copy, layout, deploy).
**Today's #2 and #3 (only if #1 finishes):**
- Investigate duplicate Stripe webhook firings.
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.
- 11d ago First seen · 144 lines · 66 tokens per session scan A 567e0e120448
standup-solo is a skill published in the GitHub repository rockscy/solo-skills (8 stars, last pushed 2mo ago), licensed MIT. It adds 66 tokens to every session and 1,223 once invoked, about $0.0003 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-31.
Other skills, from other repositories
dep-auditor
A read-only audit of a project’s third-party packages for known security issues, version health, and license facts. It uses the versions actually selected by lockfiles, which record the exact packages installed, rather than relying only on version ranges.
github-actions-gen
A guide for creating or updating GitHub Actions workflows, which are automated jobs that test, build, release, or deploy code. It first examines the real project before choosing commands, runtimes, caches, and permissions.
skill-curator
A Chinese-language evaluator for deciding whether developer tools and agent resources are suitable for a curated collection. It checks real repositories, installation paths, activity, duplicates, and security boundaries using evidence.
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
env-manager
An environment-variable manager for project settings stored outside the code, often in .env files. It checks variable definitions and usage while keeping secret values out of reports and terminal output.
error-translator
A Chinese-language assistant that translates English programming errors and explains what they mean. It covers common errors from languages and frameworks including Python, JavaScript, TypeScript, Java, and others.