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-grokgit 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-grok)<a href="https://agentmods.dev/skills/verivus-oss/sqry/sqry-grok"><img src="https://agentmods.dev/badge/skills/verivus-oss/sqry/sqry-grok/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-grok"><img src="https://agentmods.dev/badge/skills/verivus-oss/sqry/sqry-grok.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.01742 |
| Opus 5.5 | $0.00023 | $0.00697 |
| Sonnet 5.5 | $0.00012 | $0.00348 |
| Haiku 4.5 | $0.00006 | $0.00174 |
Grade E, and why
sqry-grok scanned grade E with 3 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 Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .sqry/graph .sqry/graphs .sqry/analysis 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sqry for Grok
Use this skill when the active agent is Grok and the user wants sqry v33.0.1 semantic code search.
Best path: Install the sqry plugin (.claude-plugin/ bundle). Grok Build auto-discovers it, loads all sqry skills, auto-registers sqry-mcp --no-daemon via .mcp.json, and makes scripts/doctor.sh available. Zero manual config.
Grok can still use sqry in two ways (plugin makes #2 automatic):
- CLI via shell command tools. This works whenever
sqryis installed and is the reliable fallback. - MCP tools and resources, when the Grok session has
sqry-mcpconnected (auto-configured by the plugin).
Plugin Installation (Preferred for Grok Build)
The entire sqry-skills repository is a Claude-compatible plugin (.claude-plugin/plugin.json + skills/ + .mcp.json + .lsp.json + scripts/).
git clone https://github.com/verivus-oss/sqry-skills ~/.grok/plugins/sqry- In Grok TUI:
/plugins, enablesqry, then/reload-plugins /skillsnow lists the sqry skills;/mcpsshows the auto-registeredsqryserver.- Run
~/.grok/plugins/sqry/scripts/doctor.sh --workspace .for full verification.
The plugin also works in Claude Code and any host that reads Claude plugins.
After enabling, you usually do not need the individual sqry-* skills via npx; the plugin provides them.
Setup (sqry Binary)
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
Build or refresh the index:
cd /path/to/your/project
sqry index .
sqry index --status --json .
CLI-First Usage
Use the Grok shell command tool from the workspace root. Flags go before the positional query; predicates (kind:, name:, lang:, path:) belong to sqry query:
sqry query --json 'kind:function AND name:execute'
sqry query --json 'kind:class AND lang:typescript'
sqry --json --kind class 'Manager|Executor|Recorder'
sqry graph direct-callers --json "ApprovalManager"
sqry graph direct-callees --json "main"
sqry impact --json "Executor::run"
sqry duplicates --json
sqry cycles --json
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 · 161 lines · 58 tokens per session scan E 14cbc46397ae
sqry-grok is a skill published in the GitHub repository verivus-oss/sqry (31 stars, last pushed 10d ago), licensed MIT. It adds 58 tokens to every session and 1,742 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it E with 3 findings (downloads and executes remote code, recursive force delete, 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…