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 agagniere/spekynpx agentmods add plugins/agagniere/speky/spekygit clone --depth 1 https://github.com/agagniere/spekyGrade A, and why
speky 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
{
"name": "speky",
"description": "Skills to best use Speky, the requirements and test specification manager.",
"author": {
"name": "Antoine Gagniere",
"email": "[email protected]",
"url": "https://github.com/agagniere"
},
"homepage": "https://agagniere.github.io/speky",
"repository": "https://github.com/agagniere/speky",
"license": "MIT",
"keywords": [
"specification",
"requirements"
],
"skills": [
"./claude_plugin/skills/init",
"./claude_plugin/skills/speky-workflow",
"./claude_plugin/skills/write-test-plans"
],
"agents": [
"./claude_plugin/agents/code-test-reviewer.md",
"./claude_plugin/agents/requirement-reviewer.md",
"./claude_plugin/agents/test-plan-author.md",
"./claude_plugin/agents/test-plan-reviewer.md"
],
"mcpServers": {
"speky": {
"type": "stdio",
"command": "uv",
"args": [
"run",
"speky-mcp",
"specs/spec.yaml"
],
"env": {
"UV_CACHE_DIR": "${CLAUDE_PLUGIN_DATA}/uvcache",
"UV_PROJECT": "${CLAUDE_PLUGIN_ROOT}"
}
},
"speky-selfspec": {
"type": "stdio",
"command": "uv",
"args": [
"run",
"speky-mcp",
"specs/speky.yaml",
"specs/mcp/mcp.toml"
],
"env": {
"UV_CACHE_DIR": "${CLAUDE_PLUGIN_DATA}/uvcache",
"UV_WORKING_DIR": "${CLAUDE_PLUGIN_ROOT}"
}
}
}
}
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 57 lines scan A b333e1a7b9af
speky is a plugin published in the GitHub repository agagniere/speky (2 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
greenfield
Reverse engineer clean behavioral specs from any codebase.
ypares-agent-skills
Plugin marketplace listing 6 plugins: jujutsu-skills, nix-skills, python-skills, nushell-skills, github-skills.
reqvire-org-marketplace
Official marketplace for reqvire-org plugins.
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.