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/pre-task)<a href="https://agentmods.dev/commands/frankxai/agentic-creator-os/pre-task"><img src="https://agentmods.dev/badge/commands/frankxai/agentic-creator-os/pre-task/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/frankxai/agentic-creator-os/pre-task"><img src="https://agentmods.dev/badge/commands/frankxai/agentic-creator-os/pre-task.svg" alt="Reviewed on agentmods" width="80" 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.00530 |
| Opus 5.5 | $0.00000 | $0.00212 |
| Sonnet 5.5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
pre-task 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 1mo 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.
This is a copy
100% identical to pre-task — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hook pre-task
Execute pre-task preparations and context loading.
Usage
npx claude-flow hook pre-task [options]
Options
--description, -d <text>- Task description for context--auto-spawn-agents- Automatically spawn required agents (default: true)--load-memory- Load relevant memory from previous sessions--optimize-topology- Select optimal swarm topology--estimate-complexity- Analyze task complexity
Examples
Basic pre-task hook
npx claude-flow hook pre-task --description "Implement user authentication"
With memory loading
npx claude-flow hook pre-task -d "Continue API development" --load-memory
Manual agent control
npx claude-flow hook pre-task -d "Debug issue #123" --auto-spawn-agents false
Full optimization
npx claude-flow hook pre-task -d "Refactor codebase" --optimize-topology --estimate-complexity
Features
Auto Agent Assignment
- Analyzes task requirements
- Determines needed agent types
- Spawns agents automatically
- Configures agent parameters
Memory Loading
- Retrieves relevant past decisions
- Loads previous task contexts
- Restores agent configurations
- Maintains continuity
Topology Optimization
- Analyzes task structure
- Selects best swarm topology
- Configures communication patterns
- Optimizes for performance
Complexity Estimation
- Evaluates task difficulty
- Estimates time requirements
- Suggests agent count
- Identifies dependencies
Integration
This hook is automatically called by Claude Code when:
- Starting a new task
- Resuming work after a break
- Switching between projects
- Beginning complex operations
Manual usage in agents:
# In agent coordination
npx claude-flow hook pre-task --description "Your task here"
Output
Returns JSON with:
{
"continue": true,
"topology": "hierarchical",
"agentsSpawned": 5,
"complexity": "medium",
"estimatedMinutes": 30,
"memoryLoaded": true
}
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.
- 1mo ago First seen · 112 lines · 0 tokens per session scan A 93597737b83e
pre-task is a command published in the GitHub repository frankxai/agentic-creator-os (12 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 530 tokens. A static security scan graded it A with 0 findings. It is 100% identical to pre-task, differing in 0 lines, and is treated as a copy.
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. Scope it to a release's changes with a git range ( .. ) or changes for the uncommitted working tree; audit the whole repository for the first release or…
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. Scope it to a release's changes with a git range ( .. ) or changes for the uncommitted working tree; audit the whole repository for the first…
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. check mode writes nothing and reports where the existing docs and the code disagree.
proof-points
Pull proof points from decks/battlecards, register, verify, or audit the claims your messaging relies on — then deepen brain Section 6 argument-hint: ".
experiment
Build, audit, or score a growth experiment document.
interview-summary
Summarize a customer interview transcript using JTBD analysis.