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 fpindej/netrock --skill init-verifygit clone --depth 1 https://github.com/fpindej/netrockWrote 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/fpindej/netrock/init-verify)<a href="https://agentmods.dev/skills/fpindej/netrock/init-verify"><img src="https://agentmods.dev/badge/skills/fpindej/netrock/init-verify/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/fpindej/netrock/init-verify"><img src="https://agentmods.dev/badge/skills/fpindej/netrock/init-verify.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.00058 | $0.00699 |
| Opus 5.5 | $0.00023 | $0.00280 |
| Sonnet 5.5 | $0.00012 | $0.00140 |
| Haiku 4.5 | $0.00006 | $0.00070 |
Grade C, and why
init-verify scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Delete gitignored leftovers too: the instantiation's `bin`/`obj` output is invisible to the untracked listing. Remove the renamed project trees wholesale (`rm -rf src/backend/<Name>.* src/backend/tests/<Name>.*`), then How it starts
The opening of the file, as written. The whole thing — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify template changes in a real running app. The template's placeholder form (MyProject) cannot run the full stack; a throwaway instantiation can. Nothing from the instantiation may leak into commits.
When polishing UI in the template, run /polish-ui step 5 (browser verification) inside this loop.
The loop
- Commit first: the real (pre-init, template-form) changes must be committed before anything else - the revert below destroys uncommitted work. Capture the SHA:
PRE_INIT_SHA=$(git rev-parse HEAD). - Snapshot Docker: note existing containers/volumes (
docker ps -aq,docker volume ls -q) so cleanup removes only what this run creates. - Instantiate:
./init.sh --name VerifyApp --yes --no-commit --no-build --no-aspire. Do NOT add--no-migration- the initial migration is what makes the stack actually run (it builds WebApi even with--no-build). - Run:
dotnet run --project src/backend/VerifyApp.AppHostin the background. The frontend serves at the base port (defaulthttp://localhost:13000); confirm with a probe, do not assume. - Verify: drive the browser (Playwright), capture screenshots at all required breakpoints and both themes. Save screenshots OUTSIDE the repo (scratchpad) - the revert deletes untracked repo files.
- Preview fixes cheaply: small copy/style fixes can be edited directly in the instantiated tree to preview live before teardown - these edits are throwaway, the real fix is applied pre-init afterwards.
- Teardown:
- Stop Aspire.
git reset --hard "$PRE_INIT_SHA"(the project hook blocks a baregit reset --hard- always pass the explicit target).- Delete untracked init artifacts: verify
git ls-files --others --exclude-standardlists ONLY instantiation files, then remove them (the project hook blocksgit clean- use the list +rm). - Delete gitignored leftovers too: the instantiation's
bin/objoutput is invisible to the untracked listing. Remove the renamed project trees wholesale (rm -rf src/backend/<Name>.* src/backend/tests/<Name>.*), thenfind src/backend -type d -empty -delete. - Remove the Docker containers/volumes created since the snapshot (Aspire volumes are named
<name>-db-data,<name>-storage-data).
- Apply findings pre-init: fixes discovered during verification go into the template files (normal delegation rules), then commit. Repeat the loop if the fix needs visual confirmation.
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 · 28 lines · 58 tokens per session scan C 4ebd3e4b321f
init-verify is a skill published in the GitHub repository fpindej/netrock (234 stars, last pushed 2d ago), licensed MIT. It adds 58 tokens to every session and 699 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
react-testing
Frontend testing standards using Vitest, React Testing Library, and Playwright. Use when writing UI tests.
verify
Build/launch/drive recipe for verifying apps/docs changes at runtime (demos, docs pages, llms.txt).
playwright-visual-testing
Add, repair, or review Playwright visual regression tests for browser-facing .NET apps, including screenshot baselines, Pixelmatch thresholds, deterministic rendering, and GitHub Actions artifacts. USE FOR: toHaveScreenshot, page.screenshot visual checks, Pixelmatch/pngjs comparison scripts, visual baseline updates…
lipas-e2e
Run end-to-end scenarios against a live LIPAS dev system. Use when verifying a user-visible flow works correctly across DB, Elasticsearch, app-db, and DOM. Covers municipality-user flows (create/update sports facility) and grows from there.
e2e
Prove real user journeys across browser, mobile, desktop, API and CLI surfaces using the project's existing test tools. Use for end-to-end verification, runtime UI review or requested visual proof.
ui-harness-cli
Run the Agentweaver persona-driven Playwright UI evidence harness. Use for a specific persona's deployed browser flow, end-to-end UI validation, or investigation of a UI-reported issue.