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 lukedj78/dev-flownpx agentmods add plugins/lukedj78/dev-flow/marketplacegit clone --depth 1 https://github.com/lukedj78/dev-flowGrade A, and why
dev-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": "dev-flow",
"owner": {
"name": "lucadigerlando",
"url": "https://github.com/lukedj78"
},
"metadata": {
"description": "dev-flow — the skill suite that takes a product from idea to production, over one filesystem contract."
},
"plugins": [
{
"name": "dev-flow",
"source": "./",
"description": "43 skills over one .workflow/meta.json contract: PRD → design → scaffold → modules → tests → pre-deploy gates → deploy, for Next.js 16 web, Expo/RN mobile, turborepo monorepos and an eve agent engine.",
"category": "engineering",
"keywords": [
"nextjs",
"expo",
"react-native",
"shadcn",
"eve",
"monorepo",
"gdpr",
"scrum"
]
}
]
}
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 29 lines scan A 72b545789d92
dev-flow is a plugin published in the GitHub repository lukedj78/dev-flow (5 stars, last pushed 4d 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
kiln
Multi-model software creation pipeline. A conversation becomes running, tested software — an interactive brainstorm, then an autonomous build: GPT-5.6 writes the code, Claude shapes the plans and interfaces, and each family inspects the work of the other.
sound
Code taste as installable rules. Probe a repo's stack, select only the rules its code shows a surface for (evidence-cited per rule), confirm, and scaffold a browsable .claude/sound/ rule map (surfaced by the sound:prime skill). Installed rules are user-owned; re-runs reconcile.
axint
Compile TypeScript intent definitions into native Apple App Intents and MCP tool servers. Define once, ship to Siri, Shortcuts, and Spotlight.
spec-first
Spec-first development: define a spec, implement it, and generate docs.
superpipelines-marketplace
Marketplace for the superpipelines plugin: design and run multi-agent AI pipelines.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.