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 melodic-software/claude-code-pluginsnpx agentmods add plugins/melodic-software/claude-code-plugins/naminggit clone --depth 1 https://github.com/melodic-software/claude-code-pluginsWrote 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/melodic-software/claude-code-plugins/naming)<a href="https://agentmods.dev/plugins/melodic-software/claude-code-plugins/naming"><img src="https://agentmods.dev/badge/plugins/melodic-software/claude-code-plugins/naming.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
naming 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "naming",
"version": "0.5.3",
"description": "Generates and evaluates fresh name candidates for anything — an identifier, file, module, skill, repo, or domain term — by distilling a structured context brief, fanning out blind, fresh-context generators from distinct lenses (responsibility-literal, moment-of-use, domain-lore), then scoring a shortlist against a research-ordered criteria priority resolved from the consuming org's naming criteria. The human always picks; it never auto-locks a name. An optional tournament mode adds elimination rounds with independent judges for high-stakes, hard-to-refactor names.",
"author": {
"name": "Melodic Software",
"email": "[email protected]"
},
"license": "MIT",
"keywords": [
"naming",
"name",
"rename",
"identifier",
"candidates",
"anti-anchoring",
"skill"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 153 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 21 lines scan A 01b9f4e41e96
naming is a plugin published in the GitHub repository melodic-software/claude-code-plugins (15 stars, last pushed today), 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-09-03.
Other plugins, from other repositories
problem-solving
Problem diagnosis and solution generation workflow. Separates problem clarification from solution generation for better outcomes.
ralph-wiggum
Implementation of the Ralph Wiggum technique - continuous self-referential AI loops for interactive iterative development. Run Claude in a while-true loop with the same prompt until task completion.
parallel-workflows
Parallel workflow orchestration using git worktrees for concurrent Claude Code sessions.
error-therapist
Audit and rewrite error messages to be helpful and actionable.
local-llm
Manage local Ollama LLM models for development and testing.
productivity
Session productivity skills: collaborative brainstorming, plan stress-testing, session handoff documents, and a /prime command that loads project context.