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 john-farina/claude-pluginsnpx agentmods add plugins/john-farina/claude-plugins/marketplacegit clone --depth 1 https://github.com/john-farina/claude-pluginsGrade A, and why
john-farina 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 yesterday.
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": "john-farina",
"owner": {
"name": "John Farina",
"email": "[email protected]"
},
"metadata": {
"description": "Claude Code plugins I've built and use daily — tools for building extensions, automating workflows, and making Claude smarter about your project."
},
"plugins": [
{
"name": "conjure",
"source": "./plugins/conjure",
"description": "Build Claude Code skills, agents, hooks, and MCP servers from plain-language descriptions. Generate, validate, and ship plugins without writing boilerplate.",
"version": "1.0.0",
"category": "development",
"keywords": [
"plugin-development",
"skill-generator",
"agent-builder",
"hook-builder",
"mcp-server-builder",
"scaffold",
"natural-language",
"plugin-creator",
"claude-code-plugin",
"extension-builder",
"skills",
"agents",
"hooks",
"mcp",
"developer-tools"
],
"tags": [
"plugin-dev",
"scaffold",
"generator",
"skills",
"agents",
"hooks",
"mcp",
"beginner-friendly"
]
}
]
}
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.
- yesterday First seen · 47 lines scan A 9ffb883bfe2e
john-farina is a plugin published in the GitHub repository john-farina/claude-plugins (1 stars, last pushed 3mo 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
knowledge-patch
Offline monoplugin that routes three native skills to bundled technology patches through compact generated catalogs.
nevaberry
Public marketplace for Nevaberry plugins.
marcel-bich-claude-marketplace
Plugin marketplace listing 8 plugins: credo, dogma, signal, limit, hydra.
credo
The mentor framework for Claude Code: a self-contained process layer with per-session modes, a work-item lifecycle with a hard Definition of Done, budget-aware autonomy, visual verification, and safety rules that travel into every subagent.
dogma
Intelligent sync of Claude instructions with enforcement hooks for security and consistency.
get-shit-done
Installer for the Get-Shit-Done workflow system (own secured & frozen fork, markdown skills only) - meta-prompting, context engineering and spec-driven development.