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/frankx-ai-build)<a href="https://agentmods.dev/commands/frankxai/agentic-creator-os/frankx-ai-build"><img src="https://agentmods.dev/badge/commands/frankxai/agentic-creator-os/frankx-ai-build/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/frankx-ai-build"><img src="https://agentmods.dev/badge/commands/frankxai/agentic-creator-os/frankx-ai-build.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.00017 | $0.01328 |
| Opus 5 | $0.00009 | $0.00664 |
| Sonnet 5 | $0.00003 | $0.00266 |
| Haiku 4.5 | $0.00002 | $0.00133 |
Grade A, and why
frankx-ai-build 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 7d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FrankX.AI Build Session
Purpose: Complete website build cycle from planning to deployment
Build Session Flow
PLAN → CREATE → REVIEW → DEPLOY → LOG
Step 1: Plan (5-10 min)
What are we building today?
| Build Type | Primary Command | Est. Time |
|---|---|---|
| New Article | /frankx-ai-blog |
2-3h |
| New Component | /frankx-ai-components |
1-2h |
| Product Update | /frankx-ai-products |
1-2h |
| Prompt Addition | /frankx-ai-prompts |
30m |
| SEO Optimization | /frankx-ai-seo |
1h |
| Site Improvements | /frankx-best-website |
2h+ |
| Bug Fixes | Standard dev | 30m-2h |
Quick Health Check
# Current state
git status
# Any build issues?
npm run build
# What's in progress?
cat docs/DAILY_INTELLIGENCE_OPERATIONS.md | tail -50
Priority Selection
Check these sources for today's priority:
/docs/CONTENT_ROADMAP.md- Editorial calendar/docs/PRODUCT_ORG_BLUEPRINT.md- Product priorities- Git issues/PRs - Open items
- Previous day's log - Continuity
Step 2: Create
Agent Selection
Based on build type, activate appropriate agent(s):
| Build | Lead Agent | Supporting |
|---|---|---|
| Content | Creation Engine | Technical Translator |
| Technical | Technical Translator | - |
| Music | Frequency Alchemist | Creation Engine |
| Strategy | Soul Strategist | Creation Engine |
Skill Invocation
/skill frankx-brand # Voice consistency
/skill ui-ux-design-expert # Design decisions
/skill suno-prompt-architect # Music content
/skill frontend-design:frontend-design # Components
Build Commands
Execute the appropriate command for your focus:
/frankx-ai-blog- Article creation/frankx-ai-components- UI development/frankx-ai-products- Product pages/frankx-ai-prompts- Prompt library/frankx-ai-agents- Agent-powered content
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.
- 7d ago First seen · 241 lines · 17 tokens per session scan A 75e06cc5416d
frankx-ai-build is a command published in the GitHub repository frankxai/agentic-creator-os (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 1,328 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-09-03.
Other commands, from other repositories
write-prd
Create a comprehensive Product Requirements Document from a feature idea or problem statement.
write-stories
Break a feature into backlog items — user stories, job stories, or WWA format with acceptance criteria.
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.
pre-mortem
Run a pre-mortem risk analysis on a PRD, launch plan, or feature — identify what could go wrong before it does.
stakeholder-map
Map stakeholders on a Power × Interest grid and create a tailored communication plan.
retro
Facilitate a post-launch or sprint retrospective anchored to OKRs.