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 adamjali/claude-skillsnpx agentmods add plugins/adamjali/claude-skills/skill-makergit clone --depth 1 https://github.com/adamjali/claude-skillsWrote 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/adamjali/claude-skills/skill-maker)<a href="https://agentmods.dev/plugins/adamjali/claude-skills/skill-maker"><img src="https://agentmods.dev/badge/plugins/adamjali/claude-skills/skill-maker.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
skill-maker 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 3d 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": "skill-maker",
"description": "Create new Claude Code skills or slash-commands in a clean, consistent house style — XML phases, state files, saved rules, checkpoint resumption, and 14 compaction patterns. Structured intake -> generate -> validate.",
"version": "0.1.0",
"author": { "name": "adamjali", "url": "https://github.com/adamjali" },
"homepage": "https://github.com/adamjali/claude-skills",
"license": "MIT",
"keywords": ["skills", "skill-creator", "claude-code", "scaffolding", "meta"]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 170 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.
- 3d ago First seen · 10 lines scan A 2de171a4455c
skill-maker is a plugin published in the GitHub repository adamjali/claude-skills (1 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
pm-go-to-market
Go-to-market skills for PMs: GTM strategy, growth loops, GTM motions, beachhead segments, and ideal customer profiles.
handbook-agent-spec-kit
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation.
handbook-discover
Discover and audit all plugins in a Claude Code marketplace with installation status, versions, and component breakdown.
reflect
Better alignment with LLMs.
smk marketplace
Plugin marketplace listing 13 plugins: cursor-delegate, spring-clean, portal-skills, readable, decode.
spring-clean
Two passes over a repo. spring-clean measures against a declared scoreboard, deletes or gitignores what does not belong, relocates dev docs, notes, clones and dumps to a -workspace repo, splits oversized files, draws package boundaries and writes its plan to a numbered unit list that survives a dead context. w.