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/fpindej/netrock/verifynpx skills add fpindej/netrock --skill verifygit clone --depth 1 https://github.com/fpindej/netrockWhat 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.00016 | $0.00189 |
| Opus 5 | $0.00008 | $0.00095 |
| Sonnet 5 | $0.00003 | $0.00038 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
verify 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 2d 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
/verify
Run the full post-change verification pipeline. Report the result of each step. If any step fails, stop and show the errors.
Backend (run when src/backend/ changed)
dotnet build src/backend/MyProject.slnx && dotnet test src/backend/MyProject.slnx -c Release
Frontend (run when src/frontend/ changed)
cd src/frontend && pnpm run test && pnpm run format && pnpm run lint && pnpm run check
If unsure which stack changed, run both. Fix all failures before reporting success.
For UI-visible changes, static checks are not enough: also verify in a real browser (/polish-ui step 5 describes the breakpoint/theme sweep).
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.
- 2d ago First seen · 25 lines · 16 tokens per session scan A 3db503553c07
verify is a skill published in the GitHub repository fpindej/netrock (231 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 189 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 skills, from other repositories
api-design
Guidelines for RESTful API design, endpoint naming conventions, and standardizing JSON responses.
python
Enforces FastAPI, Dependency Injection, and general Python coding standards based on the repository structure.
python-testing
Guidelines for Python testing using pytest and pytest-asyncio. Use when writing or debugging backend tests.
react
Guidelines for the React frontend, TanStack ecosystem, and React 19 standards. Use when modifying the UI.
react-testing
Frontend testing standards using Vitest, React Testing Library, and Playwright. Use when writing UI tests.
documentation
Standards for code documentation, docstrings, and maintaining README files.