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 tianemon/EasyMint --skill ui-syncgit clone --depth 1 https://github.com/tianemon/EasyMintWrote 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/tianemon/easymint/ui-sync)<a href="https://agentmods.dev/skills/tianemon/easymint/ui-sync"><img src="https://agentmods.dev/badge/skills/tianemon/easymint/ui-sync/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/tianemon/easymint/ui-sync"><img src="https://agentmods.dev/badge/skills/tianemon/easymint/ui-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00076 | $0.00642 |
| Opus 5.5 | $0.00030 | $0.00257 |
| Sonnet 5.5 | $0.00015 | $0.00128 |
| Haiku 4.5 | $0.00008 | $0.00064 |
Grade A, and why
ui-sync 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 29d 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
UI Sync — 新需求 UI 同步
用户提了新需求后，按本清单确保 UI 反映最新状态。task.json 是任务状态的真相源， UI 会自动读取它——你只需在运行时状态切换时主动调用 UI 工具。
检查清单
收到新需求后，逐项检查：
1. 是否需要追加 task？
- 小微修改（只 1 个文件、≤20 行、无新依赖、无状态机变化）→ 不写 task.json，直接做，跳到第 2 步
- 极简 / 简单档由你亲自做还是派子代理，按「执行方式判定」判（见 creation-guide skill）：极简/简单默认你亲自实现，中等及以上委派 Builder——别不管什么场景都派子代理
- 2 个及以上独立功能，或超出小微范围 → 写入 task.json，每条带
status: "pending" - 写完 task.json 后 不要 逐条调
set_task_status——pending 状态 UI 自动读取
2. 开始执行时同步运行时状态
进入编码/验收环节才调用 set_task_status，让进度条实时滚动：
- 调 Builder 或自己动手前 →
set_task_status(id, "building") - 交 Evaluator 验收前 →
set_task_status(id, "evaluating") - 你亲自实现并自验通过 →
set_task_status(id, "done")（亲自做的没有委派结果可回写，不标记进度条会停在 building） - 委派实现的验收通过/失败/中止 → 由委派执行结果自动回写，不要手动标记
何时不要调用 UI 工具
- 新增 pending 任务时（task.json 已记录，UI 自动读）
- 读取 task.json 之后（状态已在文件里）
- 重置已完成任务时（除非用户明确要求重做）
工具说明
set_task_status(taskId, status)— 手动调用时机：委派前(building)、交 Evaluator 前(evaluating)、你亲自实现并自验通过(done)；委派实现的 done / failed / aborted 由委派执行结果自动回写，不要手动标记
此工具只在 Mint 主会话可用，Builder 和 Evaluator 调不了——由你在调度前后调用。
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.
- 29d ago Changed · +2 lines 49caff73b5a6
- 1mo ago First seen · 43 lines · 76 tokens per session scan A cfb5ca71460d
ui-sync is a skill published in the GitHub repository tianemon/EasyMint (79 stars, last pushed 6d ago), licensed MIT. It adds 76 tokens to every session and 642 once invoked, about $0.0003 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-30.
Other skills, from other repositories
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
plan-pipeline
Orchestrates the complete planning pipeline: product direction (ceo-review) -> architecture (eng-review) -> implementation plan (start) -> validation (validate) -> execution (execute). Run stages individually or let the orchestrator coordinate the full flow.
routines-discover
Analyzes the current project to surface high-value Routines use cases across the three trigger types (schedule, API, GitHub events). Usage: /routines-discover.
status-report
Use when the user asks for a weekly / monthly status report, project update, individual or team progress summary. Produces a tight, scannable update with what shipped, what's in flight, what's blocked, and metrics.
linear-cli
Use when the user wants to list, view, start, create, or update Linear issues from the terminal via schpet/linear-cli, including setup, auth, repo config, and safe read/write boundaries.
orchestrator-lanes
Terminal Lane Stack Claude Code dev-orchestrator only (run-controller harness: score, DAG, run-supervisor, L0/L1/L2, wt-merge-main). Use when the session runs that terminal harness, or when $ARGUMENTS is exactly info. SKIP: Lane Pilot / BB chats (dispatch there is lanepilotdispatchwriter, LANEPILOTAGENTTYPE set)…