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.
git clone --depth 1 https://github.com/frankxai/agentic-creator-osWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/frankxai/agentic-creator-os/acos-flow)<a href="https://agentmods.dev/commands/frankxai/agentic-creator-os/acos-flow"><img src="https://agentmods.dev/badge/commands/frankxai/agentic-creator-os/acos-flow.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00000 | $0.00582 |
| Opus 5 | $0.00000 | $0.00291 |
| Sonnet 5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
acos-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 4d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ACOS Flow - System Status & Learning Dashboard
Show the full ACOS + Claude Flow system status, learning metrics, and active infrastructure.
Dashboard
Run these checks and display results:
1. Trajectory Learning
Read .claude/trajectories/ directory:
- Count completed trajectory files (exclude _active.json, _operations.jsonl, patterns.json)
- Read patterns.json for discovered patterns
- Calculate average success score across all trajectories
- Show most recent trajectory type and score
2. Learning Status
Read .claude-flow/metrics/learning-status.json if it exists.
3. Hook Pipeline Status
Read .claude/settings.json and count:
- Total hook events configured
- Total individual hooks
- Which events have matchers vs global hooks
4. Swarm Status
Read .claude-flow/swarm/agents.json for registered agents.
Check .claude-flow/swarm/messages/ for pending messages.
Check .claude-flow/swarm/handoffs/ for pending handoffs.
5. Skills & Commands
- Count global skills at
~/.agents/skills/or/mnt/c/Users/Frank/.agents/skills/ - Count skill profiles at
.claude/skills/profiles/ - Count claude-flow commands at
.claude/commands/claude-flow-*/ - Count FrankX commands at
.claude/commands/frankx-ai-*
6. Checkpoint Status
List recent checkpoints from .claude/checkpoints/
Display as a comprehensive dashboard:
══════════════════════════════════════════════════════
ACOS FLOW DASHBOARD
══════════════════════════════════════════════════════
LEARNING
Trajectories: [N] completed
Avg Success: [N%]
Patterns: [N] discovered
Last Session: [type] at [score]%
HOOKS (7 events, [N] hooks)
SessionStart: [N] hooks
UserPromptSubmit: [N] hooks
PreToolUse: [N] matchers
PostToolUse: [N] matchers
PostToolUseFailure: [N] matchers
Stop: [N] hooks
PreCompact: [N] matchers
SKILLS & COMMANDS
Global Skills: [N]
Skill Profiles: [N]
Flow Commands: [N]
FrankX Commands: [N]
SWARM
Registered Agents: [N]
Pending Messages: [N]
Pending Handoffs: [N]
CHECKPOINTS
Recent: [list last 3]
══════════════════════════════════════════════════════
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.
- 4d ago First seen · 84 lines · 0 tokens per session scan A d4e6ffb48893
acos-flow is a command published in the GitHub repository frankxai/agentic-creator-os (10 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 582 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-09-03.
Other commands, from other repositories
security-audit-static
Static security audit of AI-built code — map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks.
performance-audit-static
Static performance audit of AI-built code — find N+1 queries and request waterfalls, over-fetching, missing indexes, and caching opportunities, ranked by effort and impact.
sprint
Sprint lifecycle — plan a sprint, run a retrospective, or generate release notes.
document-app
Reverse-engineer an AI-built codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply.
analyze-test
Analyze A/B test results — statistical significance, sample size validation, and ship/extend/stop recommendations.
meeting-notes
Summarize a meeting transcript into structured notes with decisions, action items, and follow-ups.