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 forest6511/claude-code-recipes-v2 --skill daily-standupgit clone --depth 1 https://github.com/forest6511/claude-code-recipes-v2Wrote 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/forest6511/claude-code-recipes-v2/daily-standup)<a href="https://agentmods.dev/skills/forest6511/claude-code-recipes-v2/daily-standup"><img src="https://agentmods.dev/badge/skills/forest6511/claude-code-recipes-v2/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.
<a href="https://agentmods.dev/skills/forest6511/claude-code-recipes-v2/daily-standup"><img src="https://agentmods.dev/badge/skills/forest6511/claude-code-recipes-v2/daily-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.00034 | $0.00297 |
| Opus 5 | $0.00017 | $0.00148 |
| Sonnet 5 | $0.00007 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00030 |
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 9d 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
Daily Standup
進捗報告のためのテンプレート skill。effort: low で軽く動かす想定。session の model 設定を継承する (frontmatter に model を書いていないため、Opus / Sonnet どちらでも動く)。
手順
git log --since='24 hours ago' --onelineで 直近のコミットを取得gh issue list --assignee @me --state openで未完了タスクを取得- 「昨日やったこと / 今日やること / ブロッカー」の 3 カテゴリで報告
注意
- Haiku 4.5 で動かすと
effort: lowは無視される (Haiku は effort 非対応) - そのため Sonnet 以上を session の model に設定して使う運用が望ましい
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.
- 9d ago First seen · 23 lines · 34 tokens per session scan A c7716cb0ece2
daily-standup is a skill published in the GitHub repository forest6511/claude-code-recipes-v2 (5 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 297 once invoked, about $0.0002 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
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.