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 Intai/story-flownpx agentmods add plugins/intai/story-flow/design-flowgit clone --depth 1 https://github.com/Intai/story-flowGrade A, and why
design-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": "design-flow",
"description": "Agentic design workflow for collaborative product and UI design exploration",
"version": "1.0.2",
"author": {
"name": "Intai",
"email": "[email protected]"
},
"homepage": "https://github.com/Intai/story-flow/blob/main/plugins/design-flow/README.md",
"repository": "https://github.com/Intai/story-flow",
"license": "MIT",
"keywords": [
"product-design",
"ui-design",
"design-workflow",
"workflow"
]
}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 · 18 lines scan A 1c6698679126
design-flow is a plugin published in the GitHub repository Intai/story-flow (12 stars, last pushed 8d 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
dx
Developer experience essentials: GitHub Actions debugging, conversation half/quarter-cloning, context handoffs, research (Reddit and Hacker News), private GitHub search, and Claude Code version checks.
openoutreach
The OpenOutreach plugin for Claude Code — find B2B leads that fit, with the reason written out.
qamaster
Plugin marketplace listing 1 plugin: qamaster.
milestone-driver
Drives a GitHub milestone to completion: triages each issue for design gaps + dependency order up front, then for each buildable issue finds the root cause (or parks it), dispatches a TDD implementer subagent, runs unit + E2E tests + code review, opens a PR, and auto-merges issues on CI green. The whole loop sits…
parallel-lifecycle
Give every git worktree its own isolated, disposable environment (app port, ephemeral Chrome/CDP, per-worktree database) behind a single .env.worktree contract, so N agentic coding sessions build features in parallel without colliding on ports, the browser, or the database.
context-optimization
Techniques for extending effective context capacity through compaction, observation masking, KV-cache optimization, and context partitioning. Double or triple effective context without larger models.