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/bengous/claude-code-pluginsWrote 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/bengous/claude-code-plugins/research-tools)<a href="https://agentmods.dev/plugins/bengous/claude-code-plugins/research-tools"><img src="https://agentmods.dev/badge/plugins/bengous/claude-code-plugins/research-tools/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/bengous/claude-code-plugins/research-tools"><img src="https://agentmods.dev/badge/plugins/bengous/claude-code-plugins/research-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
research-tools 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 9d 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": "research-tools",
"version": "1.2.4",
"description": "Documentation research through optimal MCP sources and claim verification: research agents, source routing, web and codebase fact-checking",
"author": {
"name": "Augustin BENGOLEA",
"email": "[email protected]"
},
"homepage": "https://github.com/bengous/claude-code-plugins/tree/main/research-tools",
"repository": "https://github.com/bengous/claude-code-plugins",
"license": "MIT",
"keywords": [
"research",
"documentation",
"fact-check",
"mcp",
"context7",
"agents"
]
}
What it installs
The manifest is a name and a version. 1 skill, 4 commands, 2 agents travel with it, and installing the plugin installs all of them — 140 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 9d ago Changed d82adeac0822
- 1mo ago Changed d34fc52aad1b
- 1mo ago Changed dde5ca95f647
- 1mo ago First seen · 21 lines scan A bd4dffa1d52a
research-tools is a plugin published in the GitHub repository bengous/claude-code-plugins (6 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-03.
Other plugins, from other repositories
qiushi-skill
Qiushi Skill: methodology skills for AI agents guided by seeking truth from facts.
kit
Spec-driven Claude Code workflow with verification pipeline. Hooks, slash commands, and verification subagents.
git
Git workflow tools: commits, PRs, review inbox, checkout, and work triage.
tailscale
Tailscale CLI reference and safe patterns for exposing local services over a tailnet.
kiln
Multi-model software creation pipeline. A conversation becomes running, tested software — an interactive brainstorm, then an autonomous build: GPT-5.6 writes the code, Claude shapes the plans and interfaces, and each family inspects the work of the other.
skills
Sentimony agent skills: scope triage, planning, plan execution, test-driven development, debugging, code review, verification, and branch finishing; prose editing, dashes, and negative parallelism; skill crafting; Apache ECharts; frontend design, Vitest, TypeScript, agent context maintenance, secret hygiene, browser…