Ao Cyber Systems Devflow Claude
ao-cyber-systems-devflow-claude is a Claude Code plugin marketplace for the Build phase that ships DevFlow autonomous-agent tooling, MCP-oriented development utilities, and related media and spec-driven workflows across
by AO-Cyber-Systems · github.com/AO-Cyber-Systems/devflow-claude
Add AO-Cyber-Systems DevFlow’s Claude marketplace when you want autonomous dev agents, MCP tooling, spec-driven generation, and media helpers in one place.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install ao-cyber-systems-devflow-claude@AO-Cyber-Systems/devflow-claudeBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:AO-Cyber-Systems/devflow-claude") and the paste-ready config with skillselion.get_install_config("plugin:AO-Cyber-Systems/devflow-claude").
What it does
ao-cyber-systems-devflow-claude is a three-plugin Claude Code marketplace from AO-Cyber-Systems that advertises DevFlow as an autonomous agent and broader development toolkit. The keyword surface is broad: MCP gateways, atomic commits, parallelization, AOSentry-style guardrails, model configuration, HTML/CSS-only fallbacks, Replicate-backed imagery, video and transcription paths, and spec-driven templates for teams. For a solo builder, the practical hook is consolidating agent orchestration, context management, and generative media utilities instead of installing disparate one-off skills. It sits in Build under agent-tooling because most value lands while wiring agents, servers, and templates before you ship; ship-phase review and operate monitoring are plausible follow-ons when budgets and analytics matter. This is a curated multi-plugin marketplace, not a single narrow integration—expect more setup than a hello-world MCP server. Public catalog text does not spell every plugin name; validate each bundle member after install.
Highlights
- Marketplace bundles 3 Claude Code plugins under the DevFlow brand
- Coverage spans autonomous agents, MCP servers, skills, and team-style workflows
- Spec-driven and metaprompting-oriented generation with engineering guardrails
- Media and vision keywords include images, video, transcription, and social templates
- Spend budgets, analytics, and persistent state hints for longer agent runs
Why builders use it
Solo builders stitching agents, MCP servers, guardrails, and generative media end up with fragile glue scripts instead of one coherent devflow.
After you register the marketplace, Claude Code can draw on three DevFlow-related plugins for spec-driven agent work, integrations, and supported media pipelines under shared config patterns.
At a glance
- Type - Plugin in AI Agents.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is ao-cyber-systems-devflow-claude for?
It is for developers and small teams using Claude Code who want DevFlow autonomous agents, MCP servers, and richer generation tooling bundled together.
When should I use ao-cyber-systems-devflow-claude?
Use it during active product build when you are configuring agents, skills, budgets, and integrations—not for a one-off copy edit or static landing page.
How do I add ao-cyber-systems-devflow-claude to my agent?
Add the AO-Cyber-Systems/devflow-claude marketplace in Claude Code, install the three listed plugins, then configure MCP gateways, models, and guardrails per each plugin’s documentation.
Comments
Share how you use ao-cyber-systems-devflow-claude, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.