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 agentmods add commands/linfee/spec-kit-cn/selftestgit clone --depth 1 https://github.com/Linfee/spec-kit-cnWrote 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/commands/linfee/spec-kit-cn/selftest)<a href="https://agentmods.dev/commands/linfee/spec-kit-cn/selftest"><img src="https://agentmods.dev/badge/commands/linfee/spec-kit-cn/selftest.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 | $0.00010 | $0.00573 |
| Opus 5 | $0.00005 | $0.00287 |
| Sonnet 5 | $0.00002 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
selftest 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 4d 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
扩展自测:$ARGUMENTS
此命令用于执行一次自测,模拟开发者使用 $ARGUMENTS 扩展时的完整体验。
目标
验证扩展 $ARGUMENTS 的端到端生命周期(发现、安装、注册)。
如果 $ARGUMENTS 为空,你必须提示用户提供扩展名称,例如:/speckit.selftest.extension linear。
步骤
步骤 1:验证目录发现
检查该扩展是否存在于 Spec Kit 目录中。
执行下面的命令,并验证它成功完成,且返回的扩展 ID 与 $ARGUMENTS 完全一致。如果命令失败,或 ID 与 $ARGUMENTS 不匹配,则测试失败。
specify-cn extension info "$ARGUMENTS"
步骤 2:模拟安装
首先,尝试直接将该扩展添加到当前工作区配置中。如果目录将该扩展标记为 install_allowed: false(仅发现,不允许直接安装),那么此步骤预期会失败。
specify-cn extension add "$ARGUMENTS"
随后,通过目录中的下载 URL 来模拟添加该扩展,这应当绕过限制。
从目录元数据中获取扩展的 download_url(例如通过目录信息命令或 UI),然后运行:
specify-cn extension add "$ARGUMENTS" --from "<download_url>"
步骤 3:验证注册结果
当 add 命令完成后,通过检查项目配置来验证安装结果。
使用终端工具(如 cat)检查下面的文件是否包含 $ARGUMENTS 的注册记录。
cat .specify/extensions/.registry/$ARGUMENTS.json
步骤 4:输出验证报告
分析前面三个步骤的标准输出。 生成一种终端风格的测试输出格式,说明发现、安装和注册的结果,并直接返回给用户。
示例输出格式:
============================= test session starts ==============================
collected 3 items
test_selftest_discovery.py::test_catalog_search [PASS/FAIL]
Details: [Provide execution result of specify-cn extension search]
test_selftest_installation.py::test_extension_add [PASS/FAIL]
Details: [Provide execution result of specify-cn extension add]
test_selftest_registration.py::test_config_verification [PASS/FAIL]
Details: [Provide execution result of registry record verification]
============================== [X] passed in ... ==============================
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.
- 4d ago First seen · 70 lines · 10 tokens per session scan A 0e352b933e29
selftest is a command published in the GitHub repository Linfee/spec-kit-cn (695 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 573 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-30.
Other commands, from other repositories
verify
Run the right verification gates for what changed.
plan-spec
仅在人工明确安排 UI 自动化时,根据任务、产品规则或原型生成独立行为 Spec.
generate_application_test_plan
Khám phá ứng dụng web, sinh test plan và test scenarios. Hỗ trợ 2 mode — PLAN (chỉ test plan) và FULL (test plan + automation skeleton).
open
SoDam-Design-Kit open 대시보드 — 검증 이력·판정서·스크린샷을 브라우저로 열람 + 재검증.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.
playwright-cli
Use this skill whenever the user wants to automate a browser, scrape web content, take screenshots or PDFs of pages, fill out forms, click through UI flows, or run end-to-end tests — without using an MCP server. This skill drives Playwright directly from the bashtool via Node.js scripts. Trigger whenever the user says…