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 fledgeling-co/fledgeling-pluginsnpx agentmods add plugins/fledgeling-co/fledgeling-plugins/clarifygit clone --depth 1 https://github.com/fledgeling-co/fledgeling-pluginsGrade A, and why
clarify 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": "clarify",
"description": "Decide whether to interrupt the user with a question, then ask it so it takes one click to answer. Sweeps the conversation, the repo and earlier agent output for the answer, kills questions whose answer would not change the work, then refers every surviving technical fork to another model family before the user sees it — fable-5, gpt-5.6-sol, gemini-3.7-flash-high and grok-4.6 at xhigh, a three-family panel for genuinely open forks, and Dossier deep research for questions about the world. A fork whose axis is yours is one you settle and report, not one you ask; what reaches the user is taste, cost, scope, risk and anything irreversible, as one batched AskUserQuestion with two options and no recommendation to nudge them. Treats a note attached to an answer as binding. Ships a deterministic linter that enforces the invariant.",
"version": "1.5.0",
"author": {
"name": "Fledgeling",
"email": "[email protected]"
}
}
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 · 10 lines scan A f5345e5eadfc
clarify is a plugin published in the GitHub repository fledgeling-co/fledgeling-plugins (2 stars, last pushed 2d 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
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
claude-plugins-official
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins
Plugin marketplace listing 97 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
ecc
Plugin marketplace listing 1 plugin: ecc.
ecc
Harness-native ECC plugin for engineering teams - 68 agents, 286 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses.