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-geminigit 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-gemini)<a href="https://agentmods.dev/skills/verivus-oss/sqry/sqry-gemini"><img src="https://agentmods.dev/badge/skills/verivus-oss/sqry/sqry-gemini/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-gemini"><img src="https://agentmods.dev/badge/skills/verivus-oss/sqry/sqry-gemini.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.00050 | $0.01071 |
| Opus 5.5 | $0.00020 | $0.00428 |
| Sonnet 5.5 | $0.00010 | $0.00214 |
| Haiku 4.5 | $0.00005 | $0.00107 |
Grade D, and why
sqry-gemini scanned grade D 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 Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
This writes a global entry to `~/.gemini/settings.json` (the exact shape `--dry-run` prints): 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 This is a copy
88% identical to sqry-codex — 44 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sqry for Gemini CLI
Use this skill to configure Gemini CLI for sqry v33.0.1 MCP-backed semantic code search.
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
Index the project:
cd /path/to/your/project
sqry index .
sqry index --status --json .
Configure Gemini:
sqry mcp setup --tool gemini
sqry mcp status
Restart Gemini CLI after setup so it reloads MCP servers.
This writes a global entry to ~/.gemini/settings.json (the exact shape --dry-run prints):
{
"mcpServers": {
"sqry": {
"command": "/absolute/path/to/sqry-mcp",
"args": ["--no-daemon"],
"env": {}
}
}
}
Gemini uses global MCP config, so sqry mcp setup rejects --workspace-root for it. sqry-mcp resolves workspaces session-scoped: explicit path arguments first, then file-bearing arguments, MCP roots, last-resolved workspace, and legacy environment/CWD fallback. Start Gemini from the project directory for the simplest single-repo flow.
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. With no flag at all, sqry-mcp probes for a running sqryd and connects to it when reachable.
# Standalone: full tools + resources + prompts (preferred)
sqry-mcp --no-daemon
# Daemon: warm graph, 17-tool subset, no resources
sqry daemon start
sqry daemon load .
sqry-mcp --daemon
Set "args": ["--daemon"] only when you accept the 17-tool, no-resource tradeoff.
Skill Dependency
Also load sqry-semantic-search. It contains the shared routing rules, the table of all 39 tools with their required arguments, CLI fallback commands, ambiguity handling, output-size limits, and rebuild recovery steps.
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 · 114 lines · 50 tokens per session scan D f4bc8460c64b
sqry-gemini is a skill published in the GitHub repository verivus-oss/sqry (31 stars, last pushed 10d ago), licensed MIT. It adds 50 tokens to every session and 1,071 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it D with 3 findings (downloads and executes remote code, reads agent configuration directories, makes network calls). It is 88% identical to sqry-codex, differing in 44 lines, and is treated as a copy.
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…