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 verivus-oss/sqry --skill sqry-mistralvibegit clone --depth 1 https://github.com/verivus-oss/sqryWrote 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/verivus-oss/sqry/sqry-mistralvibe)<a href="https://agentmods.dev/skills/verivus-oss/sqry/sqry-mistralvibe"><img src="https://agentmods.dev/badge/skills/verivus-oss/sqry/sqry-mistralvibe/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/verivus-oss/sqry/sqry-mistralvibe"><img src="https://agentmods.dev/badge/skills/verivus-oss/sqry/sqry-mistralvibe.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.00068 | $0.01675 |
| Opus 5.5 | $0.00027 | $0.00670 |
| Sonnet 5.5 | $0.00014 | $0.00335 |
| Haiku 4.5 | $0.00007 | $0.00168 |
Grade C, and why
sqry-mistralvibe scanned grade C with 2 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 10d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://raw.githubusercontent.com/verivus-oss/sqry/main/scripts/install.sh | bash -s -- --component all Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://raw.githubusercontent.com/verivus-oss/sqry/main/scripts/install.sh | bash -s -- --component all How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sqry for Mistral Vibe
Use this skill to drive sqry v33.0.1 semantic code search from the Mistral Vibe CLI (vibe). The sqry CLI works in every Vibe session; MCP is configured through Vibe's TOML config when you want sqry tools available natively.
Setup
Install or upgrade sqry:
curl -fsSL https://raw.githubusercontent.com/verivus-oss/sqry/main/scripts/install.sh | bash -s -- --component all
sqry --version
sqry-mcp --version
sqry-lsp --version
sqryd --version
Install or upgrade Mistral Vibe (separate from sqry; Vibe ships via uv):
uv tool install --upgrade mistral-vibe
vibe --version
Index the project:
cd /path/to/your/project
sqry index .
sqry index --status --json .
MCP Configuration
Vibe configures MCP servers in TOML, not JSON, and sqry mcp setup has no Vibe target. Add a [[mcp_servers]] table to ~/.vibe/config.toml (Vibe uses stdio, http, and streamable-http transports; sqry runs over stdio):
[[mcp_servers]]
name = "sqry"
transport = "stdio"
command = "/absolute/path/to/sqry-mcp"
args = ["--no-daemon"]
For a project-scoped config, set VIBE_HOME to a local .vibe directory (for example export VIBE_HOME=/path/to/project/.vibe) and place config.toml there.
API keys and provider credentials live in ~/.vibe/.env, not config.toml. Vibe's CLI does not yet support MCP servers that require OAuth. sqry over stdio is unaffected.
Restart Vibe after editing config.toml. Verify with the /config command inside Vibe.
MCP mode: standalone vs daemon
Default: standalone sqry-mcp --no-daemon. Serves 39 tools, 6 MCP resources (sqry://meta/manifest and sqry://docs/*) and 6 prompts.
Daemon (sqry-mcp --daemon) warms the graph for long sessions but exposes only a 17-tool subset, zero MCP resources and zero prompts: agents cannot read sqry://meta/manifest or docs on the daemon path. Do not configure daemon then instruct reading MCP resources in the same workflow. With no flag at all, sqry-mcp probes for a running sqryd and connects to it when reachable.
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.
- 10d ago First seen · 131 lines · 68 tokens per session scan C d5398bc99239
sqry-mistralvibe is a skill published in the GitHub repository verivus-oss/sqry (31 stars, last pushed 10d ago), licensed MIT. It adds 68 tokens to every session and 1,675 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-06.
Other skills, from other repositories
tilth
Use the tilth CLI for code reading, outlining, search, callers, blast-radius deps, and structural diffs. Activate when the user asks to explore a repo, find a symbol, trace callers, read a file, view a diff, or analyze impact. Prefer tilth over grep/cat/find/ls — one invocation returns AST-aware outlines, definitions…
cocosearch-debugging
Use when debugging an error, unexpected behavior, or tracing how code flows through a system. Guides root cause analysis using CocoSearch semantic and symbol search.
cocosearch-refactoring
Use when planning a refactoring, extracting code into a new module, renaming across the codebase, or splitting a large file. Guides impact analysis and safe step-by-step execution using CocoSearch.
cocosearch-deps
Use when exploring dependency relationships, tracing file connections, analyzing change impact, or identifying hub files. Guides dependency graph exploration using CocoSearch.
use-ivygrep
Gather focused local repository context with ivygrep before implementing, debugging, reviewing, or explaining code. Use for coding tasks involving unfamiliar paths, branch changes, stack traces, architectural relationships, callers, dependents, tests, configuration, or documentation. Prefer one bounded context pack…
dekko-verify
Sanity-check a suspiciously low or zero call-graph result from dekko (getcallers, getcallees, findusages, impactedtests, unused) before concluding "no callers" or "dead code," or a heritage/throws-provenance result (query supertypes, query subtypes, query throws) that labels something (external) when you expect it to…