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 VeraTools/Vera --skill skill-v2git clone --depth 1 https://github.com/VeraTools/VeraWrote 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/veratools/vera/skill-v2)<a href="https://agentmods.dev/skills/veratools/vera/skill-v2"><img src="https://agentmods.dev/badge/skills/veratools/vera/skill-v2/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/veratools/vera/skill-v2"><img src="https://agentmods.dev/badge/skills/veratools/vera/skill-v2.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00096 | $0.00806 |
| Opus 5.5 | $0.00038 | $0.00322 |
| Sonnet 5.5 | $0.00019 | $0.00161 |
| Haiku 4.5 | $0.00010 | $0.00081 |
Grade A, and why
vera 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- vera — 100% identical, 71 lines differ
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vera
Ranked code search over an indexed repository. Results are markdown codeblocks: path:line_start-line_end symbol_type:symbol_name, then the code.
Pick the tool
| You are about to... | Do this instead |
|---|---|
| Read files to find where something lives | vera search "config object construction" |
| Read files to understand how something works | vera search "env file loading decision" |
| Find documentation on a topic | vera search "deploying behind proxy" --scope docs |
| Find every occurrence of a pattern | vera grep "TODO|FIXME" |
| Find callers or callees of a symbol | vera references make_config |
| Find definitions, routes, env reads | vera structural env / vera structural routes |
| Edit the same pattern in many files | rg |
| Read a file you already know | Read it directly |
Do not use Vera when
- You already know the exact path and line: open the file.
- You are editing across many files mechanically: use
rg. - The answer is a literal string you can match:
vera grepbeatsvera search. - You have already run two searches that returned the same region: stop searching and read the code.
Search well
- Search behavior, not nouns:
"JWT expiry handling", not"auth"or"utils". - Pass several angles in one call:
vera search "OAuth token refresh" "JWT expiry" "auth middleware". - Start broad with
--compact(signatures only, fewer tokens), then narrow with--lang,--path,--type,--limit. - Add
--intent "<goal>"when the query is vague but the goal is clear. - Scope to a change with
--changed,--since <rev>, or--base <rev>when reviewing a diff. --deeprewrites the query through an LLM; use it only after normal search misses.
Treat hits as leads
- A search hit is a lead, not evidence. Before stating how something behaves, open the cited lines.
- Follow the call graph rather than re-searching:
vera references <symbol>on a promising hit answers "who drives this" in one step. - Cite
path:linefrom code you actually read. - After editing files, run
vera update .before searching again.
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 · 64 lines · 96 tokens per session scan A 3cf838547418
vera is a skill published in the GitHub repository VeraTools/Vera (110 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 806 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-30.
Other skills, from other repositories
gno
Search local documents, files, notes, and knowledge bases. Index directories, search with BM25/vector/hybrid, get AI answers with citations. Use when user wants to search files, find documents, query notes, look up information in local folders, index a directory, set up document search, build a knowledge base, needs…
cocosearch-review-pr
Use when reviewing a GitHub PR or GitLab MR by URL. Fetches diff and metadata via API, then uses CocoSearch for blast radius analysis, dependency impact, pattern consistency, and test coverage assessment. Read-only by default; optionally pushes findings back as inline PR/MR comments after your confirmation.
cocosearch-add-language
Use when adding support for a new programming language or config format to CocoSearch. Guides through all paths (handler, symbol extraction, context expansion) with registration checklists. For grammar handlers, use cocosearch-add-grammar.
cocosearch-add-extractor
Use when adding a dependency extractor for a language or grammar. Guides through pre-checks, extractor implementation, optional module resolver, tests, and registration. Enables deps tree, deps impact, and dependency-enriched search for the target language.
cocosearch-add-grammar
Use when adding a grammar handler for domain-specific file formats that share a base language extension (e.g., GitHub Actions within YAML). Guides through YamlGrammarBase inheritance, content validation, separator spec, metadata extraction, tests, and registration.
cocosearch-commit
Use when committing changes — analyzes staged (or unstaged) diffs with CocoSearch semantic search and dependency impact to generate comprehensive Conventional Commit messages. Reviews changes thoroughly, then asks user to approve, edit, or abort the commit.