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 fledgeling-co/fledgeling-pluginsnpx agentmods add plugins/fledgeling-co/fledgeling-plugins/create-swe-projectgit clone --depth 1 https://github.com/fledgeling-co/fledgeling-pluginsGrade A, and why
create-swe-project 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 yesterday.
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": "create-swe-project",
"description": "Scaffold a complete, working new project in ~/Dev from a project idea \u2014 the slipway is where new ships are launched. Interviews up front (modules, React Native/Expo vs native SwiftUI for mobile, macOS window vs menu-bar, codename, bundle prefix, GitHub org, design reference, 1Password vault), then scaffold.sh renders ~120 templates: pnpm/Turborepo monorepo, Next.js latest, optional NestJS API, native SwiftUI macOS/iOS, optional Expo RN mobile app, design-tokens, Mongoose/Redis, Caddy dev stack, Dockerfiles, husky pre-push gate, and typecheck+build gate run. Then conducts the launch pipeline: audits docs/positioning/ (invoking /positioning:positioning if absent), generates an initial comprehensive technical PRD.md tracing all docs/features-to-triage/ briefs alongside OVERVIEW.md, designs comprehensive mocks via design-craft + ux-craft + create-mac-icon, builds a GSAP/Three.js marketing site, and packages a complete launch ops pack.",
"version": "1.12.1",
"author": {
"name": "Fledgeling",
"email": "[email protected]"
}
}
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.
- yesterday First seen · 10 lines scan A 2e3cc77df905
create-swe-project is a plugin published in the GitHub repository fledgeling-co/fledgeling-plugins (2 stars, last pushed 2d 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
xcode-build-skills
A multi-skill plugin for benchmarking and optimizing Xcode builds, compile hotspots, project settings, and Swift Package Manager dependency overhead.
ios
iOS plugin.
swift-architecture-skill
Plugin marketplace listing 1 plugin: swift-architecture-skill.
uizze
Connect Claude Code to UIZZE's focused UI references and hosted materials.
swift-testing-pro
Writes, reviews, and improves Swift Testing code using modern APIs and best practices.
kotlin-lsp
Real-time Kotlin code intelligence for Claude — instant diagnostics, go-to-definition, find references, and type info via kotlin-language-server.