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/Hulupeep/SpecflowWrote 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/hulupeep/specflow/specflow-improve)<a href="https://agentmods.dev/plugins/hulupeep/specflow/specflow-improve"><img src="https://agentmods.dev/badge/plugins/hulupeep/specflow/specflow-improve/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/hulupeep/specflow/specflow-improve"><img src="https://agentmods.dev/badge/plugins/hulupeep/specflow/specflow-improve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
specflow-improve 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": "specflow-improve",
"version": "0.1.2",
"description": "Thin authenticated Improve caller",
"author": {
"name": "Specflow"
},
"mcpServers": {
"improve": {
"command": "node",
"args": [
"${CLAUDE_PLUGIN_ROOT}/lib/bridge.cjs"
]
}
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 28 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.
- 2d ago First seen · 17 lines scan A 13e2f8f6f5cc
specflow-improve is a plugin published in the GitHub repository Hulupeep/Specflow (26 stars, last pushed today), 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-10-27.
Other plugins, from other repositories
megalinter
Set up, run and fix MegaLinter on any repository: 100+ linters for 69+ languages, 23+ formats and 21+ tooling formats, from CI or locally.
claude-plugin
Live codebase visualization and structural quality gate — 14 health dimensions graded A-F, dependency analysis, and architecture governance via MCP.
sdlc
Software Development Lifecycle standards and requirements for project quality, security, and compliance.
claudeconf
Research-driven, technology-agnostic harness generator for Claude Code: pinned, standard-tool quality + security pipelines (git hooks, CI, e2e, gates, supply-chain admission, agent-hardening) plus a read-only harness-doctor agent.
wyx
Architecture guardrails for Claude Code — automatically injects declared module boundaries into Claude's context when it edits files near a spec.
drift
Tells your coding agent when it is about to build something that already exists.