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/baodq97/open-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/baodq97/open-plugin/swe-flow)<a href="https://agentmods.dev/plugins/baodq97/open-plugin/swe-flow"><img src="https://agentmods.dev/badge/plugins/baodq97/open-plugin/swe-flow/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/baodq97/open-plugin/swe-flow"><img src="https://agentmods.dev/badge/plugins/baodq97/open-plugin/swe-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
swe-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 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
{
"name": "swe-flow",
"description": "Reusable software engineering workflow skills — goal structuring, task decomposition, planning, and execution patterns for Claude Code agents across any codebase",
"version": "0.2.0"
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 331 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.
- 1mo ago First seen · 6 lines scan A c4996198d65b
swe-flow is a plugin published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 4mo 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-31.
Other plugins, from other repositories
pm-execution
Execution and product management skills: PRDs, OKRs, roadmaps, sprints, pre-mortems, stakeholder maps, user stories, prioritization frameworks, and more.
pm-product-strategy
Product strategy skills for PMs: vision, strategy canvas, value propositions, lean canvas, business model canvas, SWOT, PESTLE, Ansoff Matrix, Porter's Five Forces, and monetization.
pm-product-discovery
Product discovery skills for PMs: ideation, experiments, assumption testing, feature prioritization, and customer interview synthesis.
handbook-structured-plan-mode
Structured planning methodology for complex feature implementations through systematic task decomposition.
ralph
PRD-to-JSON conversion and interactive user story builder for the Ralph loop.
github-cli
GitHub CLI (gh) companion: security guard blocking write operations + comprehensive usage skill for automation, API access, and workflow patterns.