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 HsuanYuLee/polaris --skill standupgit clone --depth 1 https://github.com/HsuanYuLee/polarisWrote 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/hsuanyulee/polaris/standup)<a href="https://agentmods.dev/skills/hsuanyulee/polaris/standup"><img src="https://agentmods.dev/badge/skills/hsuanyulee/polaris/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/hsuanyulee/polaris/standup"><img src="https://agentmods.dev/badge/skills/hsuanyulee/polaris/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.00156 | $0.03461 |
| Opus 5.5 | $0.00062 | $0.01384 |
| Sonnet 5.5 | $0.00031 | $0.00692 |
| Haiku 4.5 | $0.00016 | $0.00346 |
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 7d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Standup — 每日站立會議報告產生器
把一個人手上的一切收起來，統整成他自己讀得懂的四塊：YDY（昨天做了什麼）、TDT（今天要 做什麼）、BOS（被什麼卡住）、口頭同步。來源是 git、JIRA、行事曆、PR 狀態、他自己講的話。
它收一切。 工作、日常、會議、沒有單號的東西都收，不分是哪一家公司的、也不分是不是 這套工具自己的進度。要不要給別人看某一段，是拿它去報告的那個人的事，不是收集這一步的事。
送到哪由宣告決定。 有宣告就送到那裡，送出前把逐字全文交給人、等一句同意；沒有宣告就 把內容講出來，結束。細節在〈送到哪裡去〉。
Contract
standup 是 daily standup 與 EOD summary 的單一入口。它不自己做排序判斷，也不捏造資料
來源沒有的活動。它可以轉述 PR / JIRA / planning / blocker 現況，但不得自行把這些訊號升格成
workflow authority。這條有兩個方向，兩個都要擋：
- 不得升格成完成宣告——「PR 狀態良好」不等於
mergeable_ready，release page / standup 內容也不等於 release eligibility 或 release completed。 - 不得升格成待辦——狀態名、單上的現況表、一個答不了問題的查詢回空，都不構成「還有什麼
要做」。判準與三個實例在
standup-data-collection-flow.md的〈狀態不是意圖〉，這裡不抄 第二份。
這條原本只寫了第一個方向，而 2026-08-12 的四次校正有兩次是第二個方向。
收集不過濾。 這裡曾經有一段寫著「它不報產生它的那套工具自己的進度」，理由是 2026-08-14 那份對同事講了一整排跟他們無關的號碼與版本。那一段修錯了地方：問題不在 收集，在於全部倒給了同事。收集一切是給這個人自己整理用的；要給誰看哪一段，由拿它去填 某個平台、某個頁面的那一步過濾。
送到哪裡去
這支不認得任何一個特定的地方，它讀一個宣告。 那個宣告住在使用它的人自己的設定裡
（公司的 workspace-config.yaml 或個人設定），不寫死在這份散文裡。四種結果，行為互不
相同，而且每一種都要說出來：
| 讀到什麼 | 怎麼做 |
|---|---|
| 宣告齊全 | 送到那裡。送出前把逐字全文交給人、等一句同意；送出去之後要改，改動的全文再交一次 |
| 宣告在，但缺欄位 | 說出缺哪一欄，不送。內容照常產出 |
| 沒有宣告 | 把內容講出來，結束。不猜、不沿用上一個目的地 |
| 量不到（設定檔讀不到、工具不在） | 說出量不到，不當成「沒有宣告」 |
第二種與第三種不得收斂成同一句「找不到」——半條宣告比沒有宣告糟，它看起來像有人 設定過。
宣告了一個平台，就交給接手的那一支
有些團隊另外要一個平台（看板、表單），而那個平台的形狀與送出規矩由另一支 skill 帶著。
那一支是誰，也從宣告讀：設定裡 standup.platform 那一格多寫一行 handled_by，值是
那支 skill 的名字。
| 讀到什麼 | 怎麼做 |
|---|---|
standup.platform 有 handled_by |
四塊組完、本機檔寫完，就去走那一支，把四塊交給它填平台。填到送出鍵前面停下，送出由它自己的規矩決定 |
有 standup.platform，沒有 handled_by |
說出「平台宣告了，但沒說誰接手」，平台那一步不做 |
沒有 standup.platform |
照舊，四塊與本機檔就是全部 |
交棒不是可以省略的後續。 少了這一步，「寫站會」只會留下一份稿，平台那一半要靠派工的 人每天手寫「再走某一支」才補得上——那就是沒有程序。這一支不知道那一支怎麼填、也不該 知道；它只負責把人帶到那一支的門口。
目的地要什麼形狀，由那一步自己去轉，不回頭改這一支的形狀。 一個平台的表單欄位長什麼 樣是那個平台的事；把它抄進這裡，這支就只會產出那個平台的樣子。這件事發生過：2026-06 的 產出是四區塊，2026-08-13 為了對齊某個平台的表單改成一張 epic 三格，於是「每一塊收什麼」 反而沒有人寫——填的人只能照 PR 的機械狀態填。
Reference Loading
| Situation | Load |
|---|---|
| Any run | standup-data-collection-flow.md, workspace-config.yaml |
| TDT / planning | standup-planning-flow.md, standup-template.md, session-timeline.md when useful |
| Formatting | standup-format-flow.md, standup-template.md, scripts/validate-language-policy.sh |
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/session-timeline.md 3.9 KB
- references/standup-data-collection-flow.md 9.3 KB
- references/standup-format-flow.md 3.9 KB
- references/standup-planning-flow.md 14 KB
- references/standup-template.md 12 KB
- scripts/lib/main-checkout.sh 1.9 KB runs code
- scripts/lib/validate_language_policy_1.py 11 KB runs code
- scripts/lib/workspace-config-root.sh 2.6 KB runs code
- scripts/polaris-timeline.sh 7.4 KB runs code
- scripts/validate-language-policy.sh 9.2 KB runs code
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.
- 7d ago Changed · +19 lines 83df0643eee5
- 1mo ago Changed · +2 lines 1f6ab36f11a7
- 1mo ago Changed · +29 lines 66eda894f578
- 1mo ago First seen · 131 lines · 156 tokens per session scan A 1ae373dc4a91
standup is a skill published in the GitHub repository HsuanYuLee/polaris (5 stars, last pushed 2d ago), licensed MIT. It adds 156 tokens to every session and 3,461 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
prd-to-issues
A planning skill that turns an existing product requirements document, or PRD, into small GitHub Issues that developers can implement and verify. It groups work into complete user-facing slices instead of separate front-end, back-end, testing, and documentation tasks.
project-context-steward
A project-documentation skill that scans a new project or several related code repositories and records their shared context in a PROJECT_CONTEXT.md file. It captures the product, users, workflows, architecture, repository boundaries, terminology, entry points, and known pitfalls.
stylework-requirement-planning
A planning skill for reviewing a batch of product or business requests from sources such as Excel, CSV files, screenshots, or work-management exports. It groups requests by theme and records duplicates, dependencies, unclear items, and planning assumptions.
stylework-yunxiao-requirement-sync
A workflow for exporting selected requirements from Yunxiao, a project-management service, into a new sheet in an existing DingTalk online spreadsheet. It formats the result into a fixed set of columns and groups it by iteration.
strategic-alignment
Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different…
process-mapper
Use when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being…