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 skills/coffeecheese/easy-prd-testing/self-updatenpx skills add CoffeeCheese/easy-prd-testing --skill self-updategit clone --depth 1 https://github.com/CoffeeCheese/easy-prd-testingWrote 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/coffeecheese/easy-prd-testing/self-update)<a href="https://agentmods.dev/skills/coffeecheese/easy-prd-testing/self-update"><img src="https://agentmods.dev/badge/skills/coffeecheese/easy-prd-testing/self-update.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.00090 | $0.00733 |
| Opus 5 | $0.00045 | $0.00367 |
| Sonnet 5 | $0.00018 | $0.00147 |
| Haiku 4.5 | $0.00009 | $0.00073 |
Grade A, and why
self-update 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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Self Update
Use the repository updater as the only mutation engine. Keep version discovery read-only, show the confirmed release before changing files, and never improvise copy, pull, or overwrite commands.
Route The Request
- Treat phrases such as “升级版本”, “更新 Skills”, “同步最新版”, and “检查插件更新” as update intent when the object or current context is Easy PRD Testing.
- When the update object is ambiguous, ask whether the user means the complete Easy PRD Testing installation.
- For negated, hypothetical, or explanatory requests, explain the behavior without running the updater.
- Do not route “更新测试用例”, “升级测试环境”, XMind refreshes, or product-version testing here.
Check Before Confirmation
- Do not update while the current conversation is in execution-gate, test-execution, result-aggregation, or regression-testing. Ask the user to finish or stop that active workflow first.
- Resolve the repository root from this file as
../... Do not scan for other installations. - Require Node.js 18 or newer. If it is unavailable, tell the user how to install it; never install it automatically.
- Run the read-only check:
node <repository-root>/scripts/easy-prd-testing.mjs check --json
- If the installation is current, ahead, incompatible, symlinked, incomplete, or unsupported, report the returned reason and stop. Do not invent a fallback mutation.
- When an update is available, show the installation path and type, current and target versions, 3–5 release highlights, the Release Notes link, and any local changes.
Confirm Once
- Ask one explicit question to install the displayed target release.
- If a managed installation contains local modifications, state that a successful update permanently deletes them and does not keep a backup. Treat only an explicit acceptance of that loss as force authorization.
- Never force-update a Git installation with changes.
- Do not treat a vague acknowledgement as permission to add
--force.
Install The Confirmed Release
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.
- 4d ago First seen · 59 lines · 90 tokens per session scan A 10c7ce25340f
self-update is a skill published in the GitHub repository CoffeeCheese/easy-prd-testing (2 stars, last pushed 23d ago), licensed MIT. It adds 90 tokens to every session and 733 once invoked, about $0.0005 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
add-community-extension
Add a community extension to the Spec Kit catalog from a GitHub issue submission. USE FOR: processing extension submission issues, validating catalog entries, updating catalog.community.json and docs/community/extensions.md, creating PRs. DO NOT USE FOR: creating new extensions from scratch, or first-party extension…
playwright-dev
Explains how to develop Playwright - add APIs, MCP tools, CLI commands, and vendor dependencies.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
release-openspec
Use this skill when releasing OpenSpec: audit merged work and changeset coverage, decide whether a catch-up changeset PR is needed, prepare or resume the Changesets Version Packages PR, cut a beta or stable release, verify publishing, and polish GitHub release notes. Also use when asked whether an open release PR is…
playwright-devops
DevOps workflows for Playwright - CI failure analysis, workflow debugging, and release operations.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.