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 jeffrigby/somepulp-agentsnpx agentmods add plugins/jeffrigby/somepulp-agents/research-assistantgit clone --depth 1 https://github.com/jeffrigby/somepulp-agentsGrade A, and why
research-assistant 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 2d 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "research-assistant",
"displayName": "Research Assistant",
"version": "1.4.0",
"description": "Research libraries, frameworks, and APIs using official documentation. Includes /research for comprehensive investigation and /official-docs for pre-task doc lookups. Works best with Context7 and Fetch MCP servers installed (falls back to WebSearch/WebFetch if unavailable).",
"author": {
"name": "Some Pulp LLC",
"url": "https://github.com/jeffrigby"
},
"homepage": "https://github.com/jeffrigby/somepulp-agents",
"repository": "https://github.com/jeffrigby/somepulp-agents",
"license": "MIT",
"keywords": ["research", "documentation", "libraries", "apis", "official-docs", "pre-task"]
}
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.
- 2d ago First seen · 16 lines scan A 1c4f4b8f5876
research-assistant is a plugin published in the GitHub repository jeffrigby/somepulp-agents (7 stars, last pushed 1mo 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-08-31.
Other plugins, from other repositories
skillet
A skillet full of agent skills for repo audits, publish gates, execution discipline, memory handoffs, and decision-ready briefs.
skillet
Production-tested skills for auditing, improving, shipping, and preserving repo memory with AI coding agents.
code-audit-protocol
Plugin marketplace listing 1 plugin: audit-protocol.
audit-protocol
Audits a code change against a 54-phase failure taxonomy and reports what it did not check, not just what it found. Domain overlays run first and force critical-path treatment.
craftsman-marketplace
Practical, opinionated craft skills for Claude Code and Codex: engineering-readiness audits for AI-built apps, and CPA-grade US tax and accounting workpapers.
craftsman
Ship something with Lovable, Replit, Bolt, v0, Claude Code, or Codex and it works, but nobody with an engineering background has checked it. This is the engineering review you'd get from the technical co-founder you don't have. craft-audit checks the whole project across ten areas: UX, frontend, backend, database…