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 spences10/my-pi --skill pi-validation-flowgit clone --depth 1 https://github.com/spences10/my-piWrote 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/spences10/my-pi/pi-validation-flow)<a href="https://agentmods.dev/skills/spences10/my-pi/pi-validation-flow"><img src="https://agentmods.dev/badge/skills/spences10/my-pi/pi-validation-flow/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/spences10/my-pi/pi-validation-flow"><img src="https://agentmods.dev/badge/skills/spences10/my-pi/pi-validation-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 31 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00037 | $0.00371 |
| Opus 5.5 | $0.00015 | $0.00148 |
| Sonnet 5.5 | $0.00007 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
pi-validation-flow 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 19d 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
Pi Validation Flow
Validate after the final relevant edit. Reuse passed checks for completion, review, commit, and push if file contents, dependencies, configuration, and relevant environment are unchanged. Verify inputs, not just file names. Rerun only affected or previously missing checks.
Workflow
- Inspect
git status --shortandgit diff --name-only HEAD. - Run the narrowest package validation for changed packages.
- Run LSP diagnostics for changed TypeScript/Svelte source files.
- Use root validation for shared files, root scripts, package manifests, lockfile, or built-in registry changes; do not repeat package checks it already covers.
- Report failures honestly: separate new failures, pre-existing failures, skipped checks, and unavailable tools.
Command selection
- Single package:
pnpm --filter @spences10/<pkg> run check:selfandtest:self. - Root/shared changes:
pnpm run check. - Boundary-sensitive changes:
pnpm run check:boundariesunless already covered by root validation. - Svelte files: use Svelte-specific validation and LSP diagnostics.
- Skills: run
pnpx check-skills validate .agents --recursive --jsononce after the final skill edit.
Reporting format
Keep the final report short:
- Changed: files/packages touched.
- Validation: commands run or reused and results.
- Risks: only unresolved failures or skipped checks.
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.
- 19d ago Changed · +4 lines d0a74ef82a51
- 1mo ago First seen · 41 lines · 37 tokens per session scan A 8510e1eccb67
pi-validation-flow is a skill published in the GitHub repository spences10/my-pi (137 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 371 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
tmux-manual-qa
Run a single manual tmux-based QA scenario for the todo continuation feature against the real CLI (./pi-test.sh) in an interactive TUI. Captures scrollback, asserts deterministic pass/fail count markers, and cleans up test fixtures. Use only for the manual-qa milestone features.
pi
Use when needing a minimal, extensible terminal AI coding agent harness in TypeScript with plugin architecture. Pi: minimalist terminal AI coding agent emphasizing simplicity and composability.
test-browser
Run browser tests on pages affected by current PR or branch.
test-xcode
Build and test iOS apps on simulator using XcodeBuildMCP.
testing-reviewer
Always-on code-review persona. Reviews code for test coverage gaps, weak assertions, brittle implementation-coupled tests, and missing edge case coverage. Spawned by the ce:review-beta skill as part of a reviewer ensemble.
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.