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/marcusgoll/Spec-FlowWrote 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/marcusgoll/spec-flow/gemini-extension)<a href="https://agentmods.dev/plugins/marcusgoll/spec-flow/gemini-extension"><img src="https://agentmods.dev/badge/plugins/marcusgoll/spec-flow/gemini-extension/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/marcusgoll/spec-flow/gemini-extension"><img src="https://agentmods.dev/badge/plugins/marcusgoll/spec-flow/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
spec-flow 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": "spec-flow",
"version": "1.0.0",
"description": "Spec-Driven Development workflow toolkit for Gemini CLI - Ported from Claude Code",
"contextFiles": [
"GEMINI.md",
"AGENTS.md",
"package.json"
],
"instructions": "You are the Spec-Flow Orchestrator. Your goal is to guide the user through the software development lifecycle using the Spec-Flow methodology. Follow the instructions in GEMINI.md strictly."
}
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 · 12 lines scan A de8207d40c6d
spec-flow is a plugin published in the GitHub repository marcusgoll/Spec-Flow (93 stars, last pushed yesterday), 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-09-11.
Other plugins, from other repositories
audio-hooks
Audio notifications + AI-controlled config for Claude Code, Cursor IDE, and Codex CLI events. 39 hook events + 44 matcher variants, each with its own sound. Desktop toasts, TTS, webhooks, status line + per-subagent rows, rate-limit alerts. Auto-bridges to Cursor IDE 3.2.16+; native install via 'audio-hooks install…
smart-approval
AI permission tier for Claude Code Bash commands: deny-list gate plus smart AI evaluation for unknown commands. Requires Claude Code >= 2.0.45, shfmt, jq (brew install shfmt jq).
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.
humanizer
Rewrite AI-sounding text so it reads naturally without changing what it says.