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 guofu-shiqu/ux-expert-skills --skill exp-metric-designgit clone --depth 1 https://github.com/guofu-shiqu/ux-expert-skillsWrote 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/guofu-shiqu/ux-expert-skills/exp-metric-design)<a href="https://agentmods.dev/skills/guofu-shiqu/ux-expert-skills/exp-metric-design"><img src="https://agentmods.dev/badge/skills/guofu-shiqu/ux-expert-skills/exp-metric-design/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/guofu-shiqu/ux-expert-skills/exp-metric-design"><img src="https://agentmods.dev/badge/skills/guofu-shiqu/ux-expert-skills/exp-metric-design.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.00026 | $0.00588 |
| Opus 5 | $0.00013 | $0.00294 |
| Sonnet 5 | $0.00005 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
exp-metric-design 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 12d 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
体验指标体系设计
从体验感知、行为、服务效率、质量和员工体验五类指标中选取合适的指标，定义计算方式和预警机制。
触发条件
- 需要为一组体验问题建立可测量的判断标准
- 需要设计体验指标体系
- 需要定义指标的计算方式和数据来源
- 需要建立预警和响应机制
核心能力
指标分类
从以下五类指标中选取合适的指标：
| 指标类别 | 说明 | 示例 |
|---|---|---|
| 体验感知指标 | 用户主观感受 | CSAT、NPS、CES |
| 行为指标 | 用户客观行为 | 转化率、留存率、使用频率 |
| 服务效率指标 | 服务交付效率 | 首次响应时间、解决时长 |
| 质量指标 | 服务/产品质量 | 错误率、可用性、稳定性 |
| 员工体验指标 | 员工侧的体验 | eNPS、员工满意度 |
指标设计要素
为每个指标定义以下要素：
- 指标定义 — 这个指标衡量什么
- 适用场景 — 在什么场景下使用这个指标
- 数据来源 — 数据从哪里获取
- 计算方式 — 如何计算这个指标
- 预警阈值 — 什么数值需要预警
- 关联痛点 — 这个指标关联什么体验问题
- 责任方 — 谁负责改善这个指标
- 响应动作 — 指标异常时应该做什么
输出格式：指标卡
【指标卡】
▸ 指标名称：[...]
▸ 指标定义：[...]
▸ 适用场景：[...]
▸ 数据来源：[...]
▸ 计算方式：
[公式或计算逻辑]
▸ 预警阈值：
优秀：[...]
良好：[...]
需改善：[...]
▸ 关联痛点：[这个指标关联什么体验问题]
▸ 责任方：[谁负责改善这个指标]
▸ 响应动作：[指标异常时应该做什么]
▸ 复盘方式：[如何定期复盘这个指标]
使用方法
当需要为体验问题建立可测量的判断标准时，调用本 skill 设计指标体系，定义每个指标的计算方式和预警机制。
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.
- 12d ago First seen · 70 lines · 26 tokens per session scan A fa4c4523d437
exp-metric-design is a skill published in the GitHub repository guofu-shiqu/ux-expert-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 588 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
api-design
Design public interfaces for libraries and tools that other people depend on. Use when designing or reviewing a public API surface, deciding what to export, naming functions and CLI flags, adding configuration options, planning deprecations, or when the user asks "is this a good API" or "how do I change this without…
code-review
Review a pull request the way a good open-source maintainer does. Use when reviewing an incoming PR, when the user asks "review this PR" or "is this ready to merge", when triaging a stale PR queue, or when writing review feedback to an external contributor. Covers what to check and in what order, severity levels…
governance-and-sustainability
Keep a project and its maintainers alive over years. Use when deciding how decisions get made, writing GOVERNANCE.md or a code of conduct enforcement process, adding or removing maintainers, handling burnout or stepping away, setting up funding (GitHub Sponsors, Open Collective, a foundation), handling a fork or a…
open-source
Generates the complete open-source governance of a repository: README, LICENSE, REUSE.toml and SPDX headers, CONTRIBUTING, SECURITY, CODEOFCONDUCT, GOVERNANCE, CHANGELOG, .github issue/PR templates, GitHub Actions, Dependabot, conventional commits, GPG/DCO signing, git flow and ADRs. Use whenever the user wants to…
contributor-experience
Turn users into contributors and make their first PR succeed. Use when a project gets stars but no contributions, when first-time PRs stall or get abandoned, when writing or improving CONTRIBUTING.md, when setting up a dev environment that works on the first try, or when the user asks "how do I get contributors" or…
dependency-hygiene
Manage a project's dependencies so they stay small, current, and safe. Use when deciding whether to add a dependency, auditing an existing dependency tree, configuring Dependabot or Renovate, dealing with upgrade churn or a flood of bot PRs, resolving version conflicts, choosing between dependency ranges and pinning…