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 jcmrs/claude-code-spec-kit-subagent-pluginnpx agentmods add plugins/jcmrs/claude-code-spec-kit-subagent-plugin/marketplacegit clone --depth 1 https://github.com/jcmrs/claude-code-spec-kit-subagent-pluginGrade 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 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
{
"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.
- 3d 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 10mo 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
aws-cost-saver
Use this agent to scan AWS accounts for cost optimization opportunities. Features 173 automated checks across 11 domains with AWS Compute Optimizer ML integration, data transfer analysis, and reservation recommendations. Includes Zero Hallucination Pricing System with 21 anti-hallucination rules for accurate savings…
ai-engineer
Use this agent when implementing AI/ML features, integrating language models, building recommendation systems, or adding intelligent automation to applications. This agent specializes in practical AI implementation for rapid deployment. Examples:\n\n \nContext: Adding AI features to an app\nuser: "We need AI-po.
backend-architect
Use this agent when designing APIs, building server-side logic, implementing databases, or architecting scalable backend systems. This agent specializes in creating robust, secure, and performant backend services. Examples:\n\n \nContext: Designing a new API\nuser: "We need an API for our social sharing feature.
alphai
AI-enriched financial news, SEC Form 4 insider trades & market signals for your agent — hosted AlphaAI MCP + ready-made skills.
analytics-reporter
Use this agent when analyzing metrics, generating insights from data, creating performance reports, or making data-driven recommendations. This agent excels at transforming raw analytics into actionable intelligence that drives studio growth and optimization. Examples:\n\n \nContext: Monthly performance review.
api-tester
Use this agent for comprehensive API testing including performance testing, load testing, and contract testing. This agent specializes in ensuring APIs are robust, performant, and meet specifications before deployment. Examples:\n\n \nContext: Testing API performance under load.