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 FlameskyDexive/Legends-Of-Heroes --skill et-test-writegit clone --depth 1 https://github.com/FlameskyDexive/Legends-Of-HeroesWrote 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/flameskydexive/legends-of-heroes/et-test-write)<a href="https://agentmods.dev/skills/flameskydexive/legends-of-heroes/et-test-write"><img src="https://agentmods.dev/badge/skills/flameskydexive/legends-of-heroes/et-test-write/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/flameskydexive/legends-of-heroes/et-test-write"><img src="https://agentmods.dev/badge/skills/flameskydexive/legends-of-heroes/et-test-write.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.00060 | $0.00849 |
| Opus 5 | $0.00030 | $0.00425 |
| Sonnet 5 | $0.00012 | $0.00170 |
| Haiku 4.5 | $0.00006 | $0.00085 |
Grade A, and why
et-test-write 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
et-test-write - 测试编写入口
何时使用
- 编写新的
ATestHandler测试用例。 - 修改现有测试用例。
- 补
Test.md或最小验证清单。
不要加载
- 只是执行测试或查看日志:用
et-test-run。 - 只是做完整 TDD 流程编排:用
et-tdd。
落点与命名
- 测试优先放在被测功能自己的 package 内:
Packages/cn.etetet.{被测包}/Scripts/Hotfix/Test/。 - 测试专用的数据结构、Entity、Component、BT 节点或辅助模型类型必须放在被测包的
Scripts/Model/Test/。 Scripts/Model/Share/只放运行时或配置编译需要的公共模型,不放只为测试声明的类型。Scripts/Hotfix/Test/只放测试入口和测试流程代码,不放测试专用模型数据结构。cn.etetet.test只承载测试框架、公共测试基础设施,以及测试 test 包自身代码的测试;功能包测试和跨包集成测试不要临时放到 test 包。- 跨包集成测试必须放到拥有该集成场景的业务包;若确实是多业务编排,放到发起该编排的更高层业务包。
- 类名遵守
{PackageType}_{TestName}_Test,并与所在包PackageType常量匹配。 - 移动测试专用 C# 文件时同步移动
.meta,并通过 UnityBridgeRegenProject或项目既有流程刷新工程引用。
编写规则
- 测试必须是协程式、逻辑确定的验证:按真实时序
await消费事件、消息返回或明确完成信号。 - 禁止用固定时间等待、sleep、轮询、
WaitMatch或无序过滤来等待状态出现。 - ObjectWait 必须按真实时序逐个消费事件;事件桥接器只做转发,不写业务过滤。
- 含
await的测试必须在await后通过EntityRef重新获取 Entity。 - 测试需要的 Config 数据必须由测试自己用代码构造,不要修改已有 Excel、配置文件或导出的配置代码。
- 成功返回
ErrorCode.ERR_Success;失败直接返回唯一数字错误码,不污染正式ErrorCode.cs。 - 测试失败用
Log.Console,普通信息用Log.Debug,日志统一英文。
常见错误
- 把功能包自己的测试或跨包集成测试写到
cn.etetet.test。 - 把测试专用数据结构、Entity、Component、BT 节点或辅助模型类型放到
Scripts/Model/Share/或Scripts/Hotfix/Test/。 - 测试类名前缀与所在包
PackageType不一致。 await后直接访问旧 Entity。- 不同失败分支返回相同错误码。
- 用
Log.Error代替Log.Console。 - 修改已有配置文件、Excel 表或导出的配置代码准备测试数据。
- 使用固定时间等待某种状态出现。
- 使用睡眠轮询、
WaitMatch或无序过滤跳过事件。 - 在正式包
ErrorCode.cs里定义测试专用错误码。
What ships with it
1 file 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.
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 · 52 lines · 60 tokens per session scan A 428daddefc3d
et-test-write is a skill published in the GitHub repository FlameskyDexive/Legends-Of-Heroes (925 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 849 once invoked, about $0.0003 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
author-test
Generate a test given sample. Parameters: C# SDK repository root; Package name: one of Azure.AI.Projects, Azure.AI.Projects.Agents or Azure.AI.Extensions.OpenAI; the sample to use as a starting point for the test.
migrate-mstest-v3-to-v4
Use this skill before answering, planning, or editing any MSTest 3.x-to-4.x upgrade or post-upgrade failure. Triggers include "MSTest v4 breaking changes"; CS0507/CS0103/CS1061/CS1615; ExecuteAsync, CallerInfo, DisplayName, or custom TestMethodAttribute; ClassCleanupBehavior; ContainsKey; ThrowsExactly or…
migrate-mstest-v1v2-to-v3
Use this skill before answering or editing whenever an MSTest v1/v2 project is being upgraded or repaired for v3. Triggers include QualityTools assembly references; MSTest.TestFramework/TestAdapter 1.x-2.x; "upgrade to MSTest v3"; comparing v1 and v2 migration paths; choosing MSTest or MSTest.Sdk; CS0411/CS1503 after…
writing-mstest-tests
ALWAYS USE when asked to fix, rewrite, update, improve, modernize, show corrected code for, or explain existing MSTest tests or MSTest-specific configuration. Use for "review" when corrected code or edits are wanted, even for one pasted assertion or passing tests with bad failure output. Covers expected/actual labels…
migrate-xunit-to-mstest
Convert .NET tests from xUnit.net v2/v3 to MSTest v4 while preserving VSTest or MTP. Use for replacing xunit packages, Fact/Theory/InlineData/MemberData, assertions, IClassFixture/ICollectionFixture, ITestOutputHelper, TestContext cancellation, traits/Owner, skips, timeouts, and xUnit parallelization. Also use when a…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…