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 cyn-zhang/job-radar --skill source-command-standupgit clone --depth 1 https://github.com/cyn-zhang/job-radarWrote 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/cyn-zhang/job-radar/source-command-standup)<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.
<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>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.00021 | $0.00731 |
| Opus 5 | $0.00010 | $0.00365 |
| Sonnet 5 | $0.00004 | $0.00146 |
| Haiku 4.5 | $0.00002 | $0.00073 |
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.
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 — 读取上下文
在开始站会前,静默读取以下文件:
pm/sprints/sprint-XX/planning.md— 当前 sprint 任务列表和状态pm/sprints/sprint-XX/daily/— 最近一次日志(昨天)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 💪
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
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 · 128 lines · 21 tokens per session scan A 65946f651e7e
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.
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…
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…
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.
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…
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…
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…