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/voro6yov/spec-driven-developmentWrote 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/voro6yov/spec-driven-development/spec-core)<a href="https://agentmods.dev/plugins/voro6yov/spec-driven-development/spec-core"><img src="https://agentmods.dev/badge/plugins/voro6yov/spec-driven-development/spec-core/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/voro6yov/spec-driven-development/spec-core"><img src="https://agentmods.dev/badge/plugins/voro6yov/spec-driven-development/spec-core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
spec-core 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 12d 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": "spec-core",
"description": "Shared base conventions, agents, and reference modules for the spec-driven-development plugins (cross-plugin naming, layout, target-location resolution, and the copied runtime-contract modules)",
"version": "0.9.1",
"author": {
"name": "Valentin Vorobyov",
"email": "[email protected]",
"url": "https://github.com/voro6yov"
}
}
What it installs
The manifest is a name and a version. 3 skills, 2 agents travel with it, and installing the plugin installs all of them — 294 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.
- 12d ago First seen · 11 lines scan A 8c0a64a55e82
spec-core is a plugin published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 13d ago), licensed Apache-2.0. 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-10-04.
Other plugins, from other repositories
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
themes-example
themes-example. An open-source AI agent that brings the power of Gemini directly into your terminal.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins marketplace
Plugin marketplace listing 123 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
superpowers
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques.