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/artyomsv/quil/verifynpx skills add artyomsv/quil --skill verifygit clone --depth 1 https://github.com/artyomsv/quilWrote 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/artyomsv/quil/verify)<a href="https://agentmods.dev/skills/artyomsv/quil/verify"><img src="https://agentmods.dev/badge/skills/artyomsv/quil/verify.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.00027 | $0.00689 |
| Opus 5 | $0.00014 | $0.00345 |
| Sonnet 5 | $0.00005 | $0.00138 |
| Haiku 4.5 | $0.00003 | $0.00069 |
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 3d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verifying quil changes
Quil is a Go client-daemon TUI. Host has no Go/make — everything runs in Docker.
Build (dev binaries, review-fix aware)
CRLF in shell scripts breaks ./scripts/dev.sh build; build directly:
MSYS_NO_PATHCONV=1 docker run --rm -v "$(pwd -W):/src" -v quil-gomod:/go/pkg/mod -w //src golang:1.25-alpine sh -c \
'VER=$(cat VERSION | tr -d "\r") && F="-s -w -X main.version=$VER-dev" && \
F_DEV="$F -X main.buildDevMode=true -X main.buildLogLevel=debug -X main.daemonBinary=quild-dev" && \
GOOS=windows GOARCH=amd64 go build -ldflags "$F_DEV" -o quil-dev.exe ./cmd/quil && \
GOOS=windows GOARCH=amd64 go build -ldflags "$F_DEV" -o quild-dev.exe ./cmd/quild && echo BUILD_OK'
Windows target needs the gitignored internal/pty/winconpty/bins/{conpty.dll,OpenConsole.exe}; copy them from the main checkout if absent.
Drive the daemon surface (headless)
The full-screen TUI can't be driven headlessly here; the daemon is a real socket surface. Never touch the production daemon (~/.quil) — always dev (.quil/ in the worktree, QUIL_HOME set).
Start the dev daemon in the background (it restores .quil/workspace.json):
QUIL_HOME="$(pwd -W)/.quil" ./quild-dev.exe --background & sleep 6
Observe the real spawn/resize decisions in .quil/quild.log. Scope to the current run — the log APPENDS, it does not rotate, so old runs' lines linger:
awk '/quild v.*starting/{f=1} f' .quil/quild.log | grep -E 'spawn: pane|resize pane|panic|ERROR'
Session-resume (escaper) verification: each restored claude pane must spawn with --resume <its-own-uuid> (distinct per pane), not the shared --continue fallback.
Stop the dev daemon (kills claude children too)
taskkill //PID $(cat .quil/quild.pid) //T //F ; rm -f .quil/quild.pid .quil/quild.sock
Gotchas
-l/gofmt -lon the CRLF working tree flags every file; check the git blob (git show :path | gofmt -l /dev/stdin) instead.- What is NOT reachable headlessly: the TUI's small-pane preview render (crop/wrap), sidebar overlay compositing, cursor mapping — these are
View()-side. Cover them with theinternal/tuiunit tests that callrenderPreview/overlayRightdirectly, plus a human smoke test.
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.
- 3d ago First seen · 51 lines · 27 tokens per session scan A a4a8ac7a3018
verify is a skill published in the GitHub repository artyomsv/quil (13 stars, last pushed 8d ago), licensed Apache-2.0. It adds 27 tokens to every session and 689 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
x-testcontainers-go
Применяй каждый раз, когда интеграционный тест поднимает внешний сервис через testcontainers-go: PostgreSQL, RabbitMQ, Redis, Kafka, MongoDB, MinIO/S3; обычные Go integration tests и integration tests в BDD/godog-формате. Выбирай готовые modules вместо ручного контейнера, задавай context timeout и cleanup.
gmeasure
Benchmark and measure Go code with gmeasure — an Experiment groups named Measurements, recorded via RecordValue/RecordDuration/MeasureDuration or repeated Sample/SampleValue/SampleDuration with SamplingConfig, timed inline with a Stopwatch, summarized through GetStats/Stats (StatMin/Max/Mean/Median/StdDev…
add-go-test
Write or extend Go unit tests in this repo. Use when the user asks to add or update Go tests.
generate-resource-stubs
Generates typed Go stub files and grafana-foundation-sdk builder boilerplate for dashboards and alert rules. Use only when the user explicitly asks for stubs, generated resource skeletons, or builder boilerplate. This is scaffolding only; for designing or creating a usable dashboard with datasource discovery and…
upgrading-golang
Upgrades Go version across the entire Chainloop codebase including source files, Docker images, CI/CD workflows, and documentation. Use when the user mentions upgrading Go, golang version, or updating Go compiler version.
modern-go
Modernize Go code by applying version-appropriate idioms and APIs (gofix-style transformations). Scans go.mod for the Go version, then transforms Go source files to use modern patterns—from Go 1.0 through 1.26+. Use when the user says "现代化","现代Go语言", "地道的", "idiomatic", "modernize", "modern-go", "update Go code"…