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.
git clone --depth 1 https://github.com/QVerisAI/qveris-agent-toolkitWrote 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/plugins/qverisai/qveris-agent-toolkit/gemini-extension)<a href="https://agentmods.dev/plugins/qverisai/qveris-agent-toolkit/gemini-extension"><img src="https://agentmods.dev/badge/plugins/qverisai/qveris-agent-toolkit/gemini-extension.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
qveris 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 today.
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.
What it actually says
{
"name": "qveris",
"version": "0.14.2",
"description": "Discover, inspect, and call real-world API capabilities from Gemini CLI with QVeris.",
"mcpServers": {
"qveris": {
"httpUrl": "https://mcp.qveris.ai/mcp",
"headers": {
"Authorization": "Bearer $QVERIS_API_KEY"
}
}
},
"settings": [
{
"name": "QVeris API Key",
"description": "Your QVeris API key. Get one at https://qveris.ai/account?page=api-keys.",
"envVar": "QVERIS_API_KEY",
"sensitive": true
}
]
}
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.
- today First seen · 22 lines scan A 06a07c652d9e
qveris is a plugin published in the GitHub repository QVerisAI/qveris-agent-toolkit (260 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-07.
Other plugins, from other repositories
walkeros
Skills and MCP tools for walkerOS - the open-source event data collection platform. Learn architecture, create sources/destinations/transformers, validate events, bundle flows, and manage projects via API.
vovk
Claude Code plugin for Vovk.ts — topic-based skills covering segments, procedures, validation, SSR, and project setup.
postman
Full API lifecycle management for Claude Code. Sync collections, generate client code, discover APIs, run tests, create mocks, publish docs, and audit security. Powered by the Postman MCP Server.
oas
Adaptive API code generator that learns your project patterns and syncs with OpenAPI specs.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
themes-example
themes-example. An open-source AI agent that brings the power of Gemini directly into your terminal.