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/yoanbernabeu/grepai-skillsWrote 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/yoanbernabeu/grepai-skills/grepai-trace)<a href="https://agentmods.dev/plugins/yoanbernabeu/grepai-skills/grepai-trace"><img src="https://agentmods.dev/badge/plugins/yoanbernabeu/grepai-skills/grepai-trace/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/plugins/yoanbernabeu/grepai-skills/grepai-trace"><img src="https://agentmods.dev/badge/plugins/yoanbernabeu/grepai-skills/grepai-trace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
grepai-trace 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.
What it actually says
{
"name": "grepai-trace",
"description": "Skills for call graph analysis: finding callers, callees, and building complete graphs",
"source": "./",
"strict": false,
"skills": [
"./skills/trace/grepai-trace-callers",
"./skills/trace/grepai-trace-callees",
"./skills/trace/grepai-trace-graph"
]
}What it installs
The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 83 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#grepai-trace in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 11 lines scan A 9130051188a4
grepai-trace is a plugin published in the GitHub repository yoanbernabeu/grepai-skills (22 stars, last pushed 8mo ago), 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-03.
Other plugins, from other repositories
codebase-index
Semantic code search and codebase graph tools for Claude Code.
cocosearch
Local-first hybrid semantic code search with dependency graphs and cross-repo search. Powered by CocoIndex, Tree-sitter, pgvector, and Ollama.
sqry
AST-based semantic code search (compiler-grade, not embeddings). Skills + MCP (sqry-mcp) + LSP (sqry-lsp) for Grok Build, Claude Code, and compatible agents. 37 languages, 39 tools, live resources from sqry-mcp binary.
sverklo-skill
Teaches Claude how to use sverklo's code intelligence MCP tools — semantic search, blast-radius, PR review, codebase audit, persistent memory.
qgrep-mcp
Transparent indexed code search that automatically accelerates Grep on large codebases using qgrep indexes.
sapui5-linter
Use this skill when working with the UI5 Linter (@ui5/linter) for static code analysis of SAPUI5/OpenUI5 applications and libraries. Covers setup, configuring linting rules, running the linter to detect deprecated APIs, global variable usage, CSP violations, and manifest issues. Supports autofix for deprecated API…