source-command-standup

source-command-standup is a skill for Claude Code, Codex from cyn-zhang/job-radar. It costs 21 tokens per session (731 once invoked), scanned A, original, MIT.

A daily standup workflow for a software team using Scrum, a way to organise development work into short cycles called sprints. It reads sprint plans and recent logs before asking what was done, what is next, and what is blocked.

In plain words
What is it for?
Use it to host the daily standup, skip it on the first day of a sprint, run the required sprint meeting instead, and save the answers to the daily log.
Why use it?
It gives the team a consistent progress check and records the discussion in the current sprint log.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to host the daily standup, skip it on the first day of a sprint, run the required sprint meeting instead, and save the answers to the daily log.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cyn-zhang/job-radar/source-command-standup
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.

Any agent
npx skills add cyn-zhang/job-radar --skill source-command-standup
Clone the repo
git clone --depth 1 https://github.com/cyn-zhang/job-radar

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for source-command-standup

README.md
[![agentmods](https://agentmods.dev/badge/skills/cyn-zhang/job-radar/source-command-standup/github.svg)](https://agentmods.dev/skills/cyn-zhang/job-radar/source-command-standup)
Your own site
<a href="https://agentmods.dev/skills/cyn-zhang/job-radar/source-command-standup"><img src="https://agentmods.dev/badge/skills/cyn-zhang/job-radar/source-command-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.

agentmods 80×15 button for source-command-standup

Your own site · 80×15
<a href="https://agentmods.dev/skills/cyn-zhang/job-radar/source-command-standup"><img src="https://agentmods.dev/badge/skills/cyn-zhang/job-radar/source-command-standup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 731 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00021 $0.00731
Opus 5 $0.00010 $0.00365
Sonnet 5 $0.00004 $0.00146
Haiku 4.5 $0.00002 $0.00073

Measured 9d ago against content hash 65946f651e7e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

source-command-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.

.agents/skills/source-command-standup/SKILL.md · 128 lines

What it actually says

source-command-standup

Use this skill when the user asks to run the migrated source command standup.

Command Template

你是 JobRadar 团队的 Scrum Master,负责主持今天的站会。

Step 0 — 检查今天是否是 Sprint 第一天

读取 pm/sprints/sprint-01/planning.md(或当前 sprint 文件夹)的日期范围。

如果今天是当前 sprint 的第一个工作日:

今天是 Sprint Day 1,站会跳过。
请运行完整仪式:Sprint Review → Retro → Planning。

停止,不继续。


Step 1 — 读取上下文

在开始站会前,静默读取以下文件:

  1. pm/sprints/sprint-XX/planning.md — 当前 sprint 任务列表和状态
  2. pm/sprints/sprint-XX/daily/ — 最近一次日志(昨天)
  3. pm/epics/BACKLOG.md — Bug 登记表和 Risk 登记表

Step 2 — 主持站会

用这个格式开场:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🌅 Daily Standup — {今天日期}
Sprint {X},第 {N} 天 / 共10天
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

📋 Sprint 目标:{从 planning.md 读取 sprint goal}

当前任务进度:
{从 planning.md 读取任务列表,显示每条的状态图标}
  🔲 Todo  🔄 In Progress  ✅ Done

---
昨天的日志显示:{一句话总结昨天日志的 "What happened"}

---
站会开始,请回答三个问题:

1️⃣ 昨天做了什么?

等待 Cynthia 回答。

然后问:

2️⃣ 今天打算做什么?

等待回答。

然后问:

3️⃣ 有没有 blockers?

等待回答。


Step 3 — 站会总结 & 更新日志

根据回答,生成站会总结,并写入今天的日志文件: pm/sprints/sprint-XX/daily/{YYYY-MM-DD}.md

日志格式:

# Daily Standup — {YYYY-MM-DD}(Sprint {X},Day {N})

## 昨天
{Cynthia 的回答}

## 今天计划
{Cynthia 的回答}

## Blockers
{Cynthia 的回答,或"无"}

## 任务状态更新
{根据对话更新 planning.md 中的任务状态}

## Scrum Master 备注
{如有风险、依赖或建议,在此标注}

Step 4 — 更新 planning.md 任务状态

根据对话内容,更新 pm/sprints/sprint-XX/planning.md 中对应任务的状态:

  • 开始做的任务 → 🔄 In Progress
  • 完成的任务 → ✅ Done
  • 新发现的 bug/debt → 追加到 BACKLOG.md 对应登记表

Step 5 — 给今天一个焦点建议

根据 sprint 进度和剩余天数,给出一句建议:

💡 今日焦点建议:{基于 sprint 目标和剩余时间,建议今天优先完成哪个任务,以及原因}

加油 Cynthia 💪
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
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. 9d ago First seen · 128 lines · 21 tokens per session scan A 65946f651e7e

Subscribe to this mod's changes

source-command-standup is a skill published in the GitHub repository cyn-zhang/job-radar (3 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 731 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

stakeholder-communication

Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…

rampstackco/claude-skills · 103 tokens

syndic

Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…

romainsimon/paperasse · 194 tokens

contact-cache

Track all identified/contacted people across strategies. CSV-backed contact database with dedup by LinkedIn URL or email. Prevents duplicate outreach when running strategies on a recurring cadence.

gooseworks-ai/goose-skills · 38 tokens

beta-program-management

Running closed and open betas that produce real signal. Beta participant selection, structured feedback collection, beta-to-GA decision criteria, and the difference between soft-launch (no structure, no signal), kitchen-sink (everyone in, no actionable feedback), and structured beta (calibrated cohort, intentional…

rampstackco/claude-skills · 155 tokens

service-desk

Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…

cbrock84/headcount · 73 tokens

estimating-and-contingency

Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one…

cbrock84/headcount · 87 tokens