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 YIKUAIBANZI/forge-skill --skill eval-consistencygit clone --depth 1 https://github.com/YIKUAIBANZI/forge-skillWrote 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/yikuaibanzi/forge-skill/eval-consistency)<a href="https://agentmods.dev/skills/yikuaibanzi/forge-skill/eval-consistency"><img src="https://agentmods.dev/badge/skills/yikuaibanzi/forge-skill/eval-consistency.svg" alt="Measured on agentmods" 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.00044 | $0.01095 |
| Opus 5 | $0.00022 | $0.00548 |
| Sonnet 5 | $0.00009 | $0.00219 |
| Haiku 4.5 | $0.00004 | $0.00110 |
Grade A, and why
eval-consistency 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
/eval-consistency — 角色扮演一致性评测
你的任务是对 use-persona 的角色扮演质量做一次系统性评测,全程在当前对话中完成,不需要调用任何外部 API。
Step 0:加载测试资源
- 读取测试用例文件:
evals/test_cases/persona_consistency_cases.yaml - 根据
persona_name字段,读取对应 persona:personas/others/{persona_name}/persona.json - 从 persona.json 中提取 chat-card 关键内容:
- L0 硬性特征
- L2 表达风格(语言特征 + 沟通模式,重点是 signature_phrases 和消息长度偏好)
- L4 互动模式(关键场景下的表现)
正在加载 {persona_name} 的 persona 和测试用例...
共 {N} 个场景待测试。
Step 1:逐场景测试
对每个测试用例,执行两步:
1a. 生成角色扮演回复
以 persona 的身份回复用户消息。只输出回复本身,不加任何解释。
内部模板(不展示给用户):
你是 {persona_name}。
[chat-card 关键内容]
用户发来消息:"{user_message}"
以你的身份回复,只输出回复本身。
1b. 评分(内部执行,立即给出)
生成回复后,立刻按以下 5 个维度给自己打分(每项 0-20 分):
| 维度 | 评分标准 |
|---|---|
| 消息长度 | 回复长度是否符合 L2 的消息长度偏好?短消息风格但回了长段落扣分 |
| 口头禅命中 | 是否自然用到了 L2 的 signature_phrases?完全没有扣分 |
| 标点风格 | 标点和语气是否符合 persona 的风格描述? |
| 互动模式 | 在这个具体场景下,互动方式是否符合 L4 的 scene_responses? |
| 边界遵守 | 有没有违反 L0 的硬性特征?违反则此项得 0 分 |
给出每项分数 + 一句话说明。
Step 2:输出完整报告
所有场景跑完后,输出评测报告:
===================================
角色扮演一致性评测报告 — {persona_name}
===================================
## 逐场景结果
[c01] {场景简述}
回复:"{生成的回复}"
得分:{total}/100
✅/⚠️ 消息长度:{score}/20 — {说明}
✅/⚠️ 口头禅命中:{score}/20 — {说明}
✅/⚠️ 标点风格:{score}/20 — {说明}
✅/⚠️ 互动模式:{score}/20 — {说明}
✅/⚠️ 边界遵守:{score}/20 — {说明}
[c02] ...
---
## 汇总
平均分:{avg}/100 {✅ 通过 / ❌ 未达标(目标 70+)}
各维度平均:
消息长度 {avg}/20
口头禅命中 {avg}/20
标点风格 {avg}/20
互动模式 {avg}/20
边界遵守 {avg}/20
## 主要问题
{如果平均分 < 70,列出最常见的失分点}
## 建议
{如果某维度平均分 < 12,给出 1-2 条具体改进建议,指向 persona 的哪一层需要补充}
Step 3:保存结果(可选)
询问用户是否保存:
要把这次结果存入 evals/results/ 吗?
以后优化后可以对比。(y/n)
如果确认,写入 evals/results/consistency_{YYYYMMDD}.md。
注意
- 全程不需要 API Key:评分是你自己执行的,不是另起一个 LLM
- 评分要诚实:对自己生成的回复该扣分就扣分,不要因为是自己生成的就打高分
- 用例是基于小美的,如果用户指定了其他 persona,根据那个 persona 的 L2/L4 调整评分标准
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 · 129 lines · 44 tokens per session scan A 91b0e0f8767a
eval-consistency is a skill published in the GitHub repository YIKUAIBANZI/forge-skill (116 stars, last pushed 5mo ago), licensed MIT. It adds 44 tokens to every session and 1,095 once invoked, about $0.0002 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-30.
Other skills, from other repositories
weak-agent-test
Run the weak-agent adversarial test harness against docx-cli. Spawns weak exercise agents (Haiku by default, Sonnet to probe, or a local agent harness's pre-produced runs) to perform real document tasks over six scenarios — five editing (MNDA form-fill + font fidelity, invoice table-edit/restructure + logo replace…
declaring-invariants
Find tests that enumerate a domain by copying it, and declare the invariants a codebase depends on. Reports where a parametrize list, for-loop, or it.each iterates a hand-written subset of a dict/set/tuple/Enum that exists in the source, and names the members nothing covers. Use when reviewing tests, when a module…
gating
Build and audit deterministic verification gates — a check that blocks a pipeline and can be shown to go red. Use when writing a calibration gate, CI check, validation script or pre-publication check for a numeric or empirical result; when a plausible-but-wrong value would survive review; when asking whether an…
change-request-to-go-live-protocol
Use this skill when a Dynamics 365 change request must be structured and progressed through impact assessment, fit-gap analysis, UAT sign-off, go/no-go decision, go-live execution, and hypercare using the Success by Design framework. Defines the full change-to-go-live flow — change request intake, solution blueprint…
environment-to-production-release-protocol
Use this skill when a Power Platform or Dynamics 365 solution must progress through a structured dev-to-test-to-production release pipeline using managed solutions and Power Platform pipelines, when rollback readiness must be verified before go-live, or when a deployment approval gate must be enforced. Defines the…
erp-crm-cutover-protocol
Use this skill when a Dynamics 365 ERP or CRM implementation is approaching go-live and must progress through mock migration, data reconciliation, cutover runbook execution, rollback testing, and the Success by Design go-live gate before production switchover. Orchestrates d365-data-migration-cutover-agent as primary…