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.
/plugin marketplace add teambrilliant/claude-peeknpx agentmods add plugins/teambrilliant/claude-peek/mcpgit clone --depth 1 https://github.com/teambrilliant/claude-peekWrote 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/teambrilliant/claude-peek/mcp)<a href="https://agentmods.dev/plugins/teambrilliant/claude-peek/mcp"><img src="https://agentmods.dev/badge/plugins/teambrilliant/claude-peek/mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
claude-peek 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 4d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What it installs
The manifest is a name and a version. 1 MCP server travel with it, and installing the plugin installs all of them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json 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.
- 4d ago First seen · 6 lines scan A 27fae34a7f65
claude-peek is a plugin published in the GitHub repository teambrilliant/claude-peek (5 stars, last pushed 5mo ago), with no licence file. 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-08-31.
Other plugins, from other repositories
ensemblr
Working inside the Ensemblr desktop coding workspace: control tools, repository settings, and the workspace/worktree model.
coder-eval
Test whether your Claude Code skills actually trigger, and benchmark any coding agent — author, run, and analyze the eval suite that proves it, locally or as a CI gate.
deslop marketplace
Claude Code distribution for the deslop Agent Skill.
rudder
Maintain a device-local spec from coding-session intent, then generate focused unit tests with your existing coding agent.
engine
Skills for building applications with PlayCanvas Engine.
development
Code development and quality assurance tools - analyze, test, fix, review.