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 commands/bita71/agent-workflow-kit/symphonygit clone --depth 1 https://github.com/Bita71/Agent-Workflow-KitWhat 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.00000 | $0.00169 |
| Opus 5 | $0.00000 | $0.00084 |
| Sonnet 5 | $0.00000 | $0.00034 |
| Haiku 4.5 | $0.00000 | $0.00017 |
Grade A, and why
symphony 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
symphony
Drive the whole task through the full pipeline as the orchestrator.
Follow docs/ai/commands/symphony.md exactly: clarify → plan (Codex) → build
(subagent) → verify against the plan → parallel review → triage → fix loop → done,
with human gates and a resumable run file.
Supporting docs the command relies on:
docs/ai/agents/cli.md— canonical CLI calls (do not invent flags)docs/ai/commands/codex-plan.md,docs/ai/commands/review-full.mddocs/ai/commands/choose-model.mddocs/ai/recipes/git-worktree.mddocs/ai/rules/commit-message.md,docs/ai/runs/README.md
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 · 16 lines · 0 tokens per session scan A 1c4a8351e85e
symphony is a command published in the GitHub repository Bita71/Agent-Workflow-Kit (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 169 tokens. 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 commands, from other repositories
pr-review
Review a PR across multiple dimensions (description, code, scan, tests).
claude-md-migrate
Rewrite a bloated or stale CLAUDE.md into a lean, verified "map, not wishes" file — nothing invented, hard rules preserved verbatim.
claude-md-new
Scaffold a CLAUDE.md for this repo from battle-tested templates, filled in with the project's real commands.
setup
Generate HOTL adapter files for your team's code assistants (Codex, Cline, Cursor, Copilot).
subagent-execute
Execute a reviewed HOTL workflow in this session with delegated subagent steps and controller-owned verification.
write-plan
Create a docs/plans/YYYY-MM-DD- -workflow.md implementation workflow with loops and gates.