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/cluesmith/codevWrote 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/cluesmith/codev/mod)<a href="https://agentmods.dev/plugins/cluesmith/codev/mod"><img src="https://agentmods.dev/badge/plugins/cluesmith/codev/mod/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/cluesmith/codev/mod"><img src="https://agentmods.dev/badge/plugins/cluesmith/codev/mod.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
codev-spike 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 11d 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": "codev-spike",
"version": "0.1.0",
"description": "EXPERIMENT #1782 spike: Codev guard, attribution scrub, context band and issue peek. Never installed; loaded only by an explicit --plugin-dir.",
"types": "./types/index.d.ts",
"author": {
"name": "Codev"
}
}
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.
- 11d ago First seen · 10 lines scan A 085a428dff44
codev-spike is a plugin published in the GitHub repository cluesmith/codev (289 stars, last pushed today), licensed Apache-2.0. 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-10-06.
Other plugins, from other repositories
dx
Developer experience essentials: GitHub Actions debugging, conversation half/quarter-cloning, context handoffs, research (Reddit and Hacker News), private GitHub search, and Claude Code version checks.
agent-ready-repo marketplace
Agent skills, subagents, and hooks for Claude Code and other coding agents.
agents-meet-rl
Troubleshooter + machine-readable corpus for reinforcement-learning training, evaluation, and experiment design on LLM agents (single/multi-agent, multi-turn, tool-augmented). Distilled from the AgentsMeetRL awesome list (378 projects).
credential-brokers
Your credentials stay out of the repo and out of the agent's context. credbroker resolves them in-process, sso-broker handles the browser cookie dance, and an LLM-cooperative credential-setup skill walks you through the first time.
desk-research
Ask a question, get an answer with citations you can check. It runs from a two-minute lookup to a multi-week investigation with its own folder, and argues against its own findings before handing them over.
ooda-loop marketplace
Plugin marketplace listing 1 plugin: ooda-loop.