Borrowing it
Nothing to install: this file belongs to meltforce/vimmary. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/meltforce/vimmary/main/.claude/skills/verify/SKILL.mdgit clone --depth 1 https://github.com/meltforce/vimmaryWrote 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/meltforce/vimmary/verify)<a href="https://agentmods.dev/skills/meltforce/vimmary/verify"><img src="https://agentmods.dev/badge/skills/meltforce/vimmary/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/meltforce/vimmary/verify"><img src="https://agentmods.dev/badge/skills/meltforce/vimmary/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.00102 | $0.01069 |
| Opus 5.5 | $0.00041 | $0.00428 |
| Sonnet 5.5 | $0.00020 | $0.00214 |
| Haiku 4.5 | $0.00010 | $0.00107 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify
The chain CI runs, in the order that fails fastest. Run it from the repo root before committing.
1. The embed stub comes first
web.go carries //go:embed all:web/dist, and .gitignore excludes that
directory. Every Go command below fails with an embed error on a fresh
checkout until web/dist exists — this is not a broken build, it is a missing
directory.
Either build the frontend for real (step 5, needed anyway if you touched web/),
or create the stub CI uses:
mkdir -p web/dist && touch web/dist/.gitkeep
2. Build, format and vet
CGO_ENABLED=0 go build -o /tmp/vimmary ./cmd/vimmary
gofmt -l internal/ cmd/
go vet ./...
CGO_ENABLED=0 matches the Docker image, which is built without a C toolchain.
A build that only passes with cgo enabled will fail in CI.
gofmt -l prints the files that are not formatted and nothing else — empty
output is the pass. Nothing else in this chain checks it: golangci-lint's
default set has no formatting linter, and CI runs neither. An unformatted file
was committed on 2026-08-07 (9afc86a, a misaligned struct tag in
internal/models/models.go) and no step objected.
The two files that predated this step — internal/mcp/server.go (import order)
and internal/storage/videos_integration_test.go — were formatted on
2026-08-07. gofmt -l now prints nothing on a clean tree, so any output is
from the change in front of you.
3. Tests
go test -race ./...
The storage tests need a database and do not skip locally.
internal/storage/videos_integration_test.go connects to
postgres://vimmary:vimmary@localhost:5434/vimmary, which is what
docker compose up db exposes — note the port is 5434, not 5432. Start it
first:
docker compose up -d db
Override with TEST_DATABASE_URL if the database lives elsewhere. The test skips
only when CI is set, which means CI does not cover the storage layer — a
regression there is caught locally or not at all.
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 · 107 lines · 102 tokens per session scan A 8b755554f26a
verify is a skill published in the GitHub repository meltforce/vimmary (5 stars, last pushed today), licensed MIT. It adds 102 tokens to every session and 1,069 once invoked, about $0.0004 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-31.
Other skills, from other repositories
article-summary-writer
Writes a concise summary, standfirst, abstract, or deck for a completed article at a specified length and format — capturing the essential argument and news value without spoiling the reading experience.
episode-summary-writer
Writes concise episode summaries in three lengths — platform short (100 words), directory standard (150 words), and promotional long (250 words) — for podcast directories, promotional emails, and social bios.
summarizer
Summarize URLs, PDFs, YouTube videos, and text content - extract key points and generate concise summaries.
youtube-summarizer
Summarize YouTube videos by extracting transcripts and generating structured summaries with key points, timestamps, and topic segmentation.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".