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 asysta-act/agent-flownpx agentmods add plugins/asysta-act/agent-flow/marketplacegit clone --depth 1 https://github.com/asysta-act/agent-flowGrade A, and why
agent-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": "agent-flow",
"owner": {
"name": "Filip Sabacky",
"email": "[email protected]"
},
"metadata": {
"description": "Automated bug-fix, feature, and scaffold workflows for Claude Code",
"version": "1.2.0"
},
"plugins": [
{
"name": "agent-flow",
"source": {
"source": "url",
"url": "https://github.com/asysta-act/agent-flow.git"
},
"description": "agent-flow — Claude Code plugin for automated bug-fix, feature, and scaffold workflows. Issue tracker to merged PR via a pipeline of specialized AI agents.",
"version": "1.2.0",
"license": "MIT",
"strict": true
}
]
}
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 · 25 lines scan A 6d67e4b67e1a
agent-flow is a plugin published in the GitHub repository asysta-act/agent-flow (12 stars, last pushed 1mo 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
team-up
Plugin marketplace listing 1 plugin: team-up.
agent-teams
Orchestrate multi-agent teams for parallel code review, hypothesis-driven debugging, and coordinated feature development using Claude Code's Agent Teams.
newsjack
Newsjack — PR-operator skills for coding agents.
jenkins-cli
GitHub CLI-style interface for Jenkins controllers - create multibranch jobs, inspect config.xml, and manage runs, logs, artifacts, credentials, nodes, and queues.
claude-superskills
Plugin marketplace listing 1 plugin: claude-superskills.
deepwork-plugins
Plugins for the DeepWork framework.