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 weijiafu14/pi2dsh --skill demo-skillgit clone --depth 1 https://github.com/weijiafu14/pi2dshWrote 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/weijiafu14/pi2dsh/demo-skill)<a href="https://agentmods.dev/skills/weijiafu14/pi2dsh/demo-skill"><img src="https://agentmods.dev/badge/skills/weijiafu14/pi2dsh/demo-skill/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/weijiafu14/pi2dsh/demo-skill"><img src="https://agentmods.dev/badge/skills/weijiafu14/pi2dsh/demo-skill.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.00012 | $0.00032 |
| Opus 5.5 | $0.00005 | $0.00013 |
| Sonnet 5.5 | $0.00002 | $0.00006 |
| Haiku 4.5 | $0.00001 | $0.00003 |
Grade A, and why
demo-skill 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 1mo 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
When invoked, reply with exactly SKILL-DEMO-OK.
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.
- 1mo ago First seen · 6 lines · 12 tokens per session scan A 8154c2ea4e33
demo-skill is a skill published in the GitHub repository weijiafu14/pi2dsh (216 stars, last pushed 2d ago), licensed MIT. It adds 12 tokens to every session and 32 once invoked, about $0.0000 per session on Opus 5.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-09-16.
Other skills, from other repositories
test-first
A test-first development guide, where tests are written before the code they check. TDD, or test-driven development, means first writing a test that fails, then writing the simplest code that makes it pass.
delivery-proof
Delivery proof and the doublecheck report. Use when the work is done and the delivery must be proven — consolidate the spec, test timeline, review verdicts, and verification checks into a doublecheckreport, and only then claim completion.
red-green-tdd
Red/green test discipline for implementation work. Use once a doublecheck spec is on record and implementation is about to start — write a test that fails for the missing behavior, run it to see it fail (red), make the change, run again to see it pass (green).
code2skill-review-flow
A read-only reviewer for the main user flows in a package generated by Code2Skill. It checks whether representative paths are basically usable, without proving that every source-code detail is included.
codebase-design-zh
A set of design principles for creating modules with small interfaces and substantial behaviour behind them. It explains terms such as interface, implementation, adapter, and seam in plain terms for this design approach.
dev-qa
A development and quality process for building software, testing it, and checking it for security problems. It separates implementation, quality assurance, and security review while coordinating their handoffs.