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.
npx agentmods add skills/asysta-act/agent-flow/setup-agentsnpx skills add asysta-act/agent-flow --skill setup-agentsgit clone --depth 1 https://github.com/asysta-act/agent-flowWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00018 | $0.03335 |
| Opus 5 | $0.00009 | $0.01667 |
| Sonnet 5 | $0.00004 | $0.00667 |
| Haiku 4.5 | $0.00002 | $0.00333 |
Grade A, and why
setup-agents 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.
How it starts
The opening of the file, as written. The whole thing — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/agent-flow:setup-agents
Purpose
One-shot project scanner that detects project type (Python, TypeScript, monorepo, test
framework, Java, Rust, .NET) and generates smart customization/{agent}.toml defaults
for agents in the consuming project. This is a meta-agent style one-shot tool — NOT a
continuous meta-gen architecture.
Reference: docs/guides/setup-agents-skill.md for full heuristic enumeration and worked examples.
TOML schema: core/overlay/toml-overlay.md (3-tier merge contract).
Synopsis
/agent-flow:setup-agents [--dry-run] [--yolo] [--force]
Flags:
- (no flags): scan project, preview-diff each planned file, prompt Apply / Skip / Abort before each write.
--yolo: scan and write all generated files silently (no preview prompt). Idempotent regen of# generated:files and first-time writes both apply without confirmation.--force: overwrite existing user-edited files (those WITHOUT# generated:header) after backing up to{agent}.toml.bak-{ISO-8601-timestamp}; still subject to preview prompt unless--yolois also supplied.--dry-run: scan and print planned writes to stdout; write nothing to disk.
Step 1 — Detect project root
Detect project root as the directory containing CLAUDE.md, falling back to the git
repository root (git rev-parse --show-toplevel), falling back to CWD.
if [ -f "CLAUDE.md" ]; then
PROJECT_ROOT="$(pwd)"
elif git rev-parse --show-toplevel > /dev/null 2>&1; then
PROJECT_ROOT="$(git rev-parse --show-toplevel)"
else
PROJECT_ROOT="$(pwd)"
fi
CUSTOMIZATION_DIR="${PROJECT_ROOT}/customization"
Ensure customization/ directory exists (create if absent):
mkdir -p "${CUSTOMIZATION_DIR}"
Step 2 — Project scan (heuristic detection)
Scan the project root for manifest files and framework configs. Build a detection map:
Python project detection
Trigger files: pyproject.toml, requirements.txt, setup.py
PYTHON_PROJECT=false
if [ -f "${PROJECT_ROOT}/pyproject.toml" ] || \
[ -f "${PROJECT_ROOT}/requirements.txt" ] || \
[ -f "${PROJECT_ROOT}/setup.py" ]; then
PYTHON_PROJECT=true
fi
What ships with it
1 file beside SKILL.md 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 · 336 lines · 18 tokens per session scan A 28307f8a08da
setup-agents is a skill published in the GitHub repository asysta-act/agent-flow (12 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 3,335 once invoked, about $0.0001 per session on Opus 5. 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 skills, from other repositories
team-up
Orchestrate persistent agent teams with TeamCreate. Use when the user says "team up", "spin up a team", or invokes /team-up.
cortivex-pipeline
Build and run AI agent pipelines that decompose complex tasks into coordinated agent workflows.
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
haiku
When writing a haiku for this bot, follow these conventions.