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.
git clone --depth 1 https://github.com/jcmrs/claude-code-spec-kit-subagent-pluginWrote 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/jcmrs/claude-code-spec-kit-subagent-plugin/marketplace)<a href="https://agentmods.dev/plugins/jcmrs/claude-code-spec-kit-subagent-plugin/marketplace"><img src="https://agentmods.dev/badge/plugins/jcmrs/claude-code-spec-kit-subagent-plugin/marketplace/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/jcmrs/claude-code-spec-kit-subagent-plugin/marketplace"><img src="https://agentmods.dev/badge/plugins/jcmrs/claude-code-spec-kit-subagent-plugin/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
claude-code-spec-kit-subagent-plugin marketplace 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 1mo 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
{
"display_name": "Spec Kit Partner",
"summary": "A next-generation, conversational Claude Code plugin for rigorous, multi-perspective technical spec creation using dynamic memory graphs, adaptive workflows, and multi-role analysis. Ideal for GitHub Spec Kit methodology and non-technical users.",
"description": "Spec Kit Partner is a Claude Code plugin designed to assist teams and individuals in collaboratively drafting rigorous, multi-perspective technical specifications. Leveraging dynamic memory graphs, adaptive workflows, and explicit multi-role analysis, this agentic plugin bridges human creativity and technical rigor—especially for non-technical users and those adopting the GitHub Spec Kit methodology.",
"categories": [
"ai",
"documentation",
"developer-tools",
"utilities"
],
"icon": "assets/icon.png",
"screenshots": [
"assets/screenshot1.png",
"assets/screenshot2.png"
],
"documentation_url": "https://github.com/jcmrs/claude-code-spec-kit-subagent-plugin/blob/main/README.md",
"publisher": "jcmrs",
"license": "MIT",
"source_url": "https://github.com/jcmrs/claude-code-spec-kit-subagent-plugin",
"support_url": "https://github.com/jcmrs/claude-code-spec-kit-subagent-plugin/issues",
"changelog_url": "https://github.com/jcmrs/claude-code-spec-kit-subagent-plugin/blob/main/CHANGELOG.md",
"terms_url": "",
"privacy_url": "",
"version": "1.0.0",
"min_claude_version": "1.0.0",
"max_claude_version": "",
"release_date": "2025-10-12",
"external_links": [
{
"label": "Spec Kit Methodology",
"url": "https://github.com/github/spec-kit"
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.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.
- 1mo ago First seen · 35 lines scan A e71c9dd4ee35
claude-code-spec-kit-subagent-plugin marketplace is a plugin published in the GitHub repository jcmrs/claude-code-spec-kit-subagent-plugin (22 stars, last pushed 1y 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-30.
Other plugins, from other repositories
recall
Durable, fully-local project memory for Claude Code. Logs every session to .recall/history.md and condenses it into .recall/context.md with a local Python summarizer (TF-IDF + TextRank) — no API key, no external model, nothing leaves your machine. New sessions resume from the saved context.
go-ultimate
Opinionated Go development skill — architecture, conventions, production readiness, repo/CI hygiene, review, and MCP/agent patterns.
orchestrator
Token-frugal multi-agent orchestration for Claude Code, built for a Claude Fable 5 chair: Fable plans and decides, Sonnet 5 carries the volume, Opus 5 takes the hard slices and escalations, each worker's effort sized by the chair. Delegation is the DEFAULT, not the escalation — and a solo guard watches the chair…
version-sentinel
Hard-blocks dependency additions, bumps, and downgrades until a fresh, source-cited version check is recorded. Supports npm, pip, Poetry/uv, Cargo, and NuGet.
commander-hub marketplace
Plugin marketplace listing 1 plugin: commander.
tg-voice
Transcribe Telegram voice messages using local Whisper (faster-whisper) — automatic PostToolUse hook with setup skill for installation and model download.