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/frankxai/agentic-creator-os/content-studiogit 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/content-studio)<a href="https://agentmods.dev/commands/frankxai/agentic-creator-os/content-studio"><img src="https://agentmods.dev/badge/commands/frankxai/agentic-creator-os/content-studio.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.00010 | $0.00886 |
| Opus 5 | $0.00005 | $0.00443 |
| Sonnet 5 | $0.00002 | $0.00177 |
| Haiku 4.5 | $0.00001 | $0.00089 |
Grade A, and why
content-studio 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/content-studio - Content Studio Command
Overview
Content Studio is the visual content management system for FrankX.
- Dashboard: https://frankx.ai/admin/content-studio
- Queue:
/data/content-queue/queue.json
Usage
Watch Mode (Process Queue)
/content-studio watch
Monitors the queue file and processes tasks automatically.
Generate Social Pack
/content-studio social [blog-slug]
Generates LinkedIn + Twitter content for a blog post.
Generate Images
/content-studio images [blog-slug]
Generates platform-specific images (1:1, 16:9, 9:16).
Queue Processing
When in watch mode, Claude Code will:
- Read
/data/content-queue/queue.json - Find pending tasks
- Execute the appropriate skill
- Update task status
- Commit results to repo
Task Types
| Type | Action |
|---|---|
generate_social_pack |
Run /factory social-remix for latest blog |
generate_twitter_thread |
Create Twitter thread from blog |
generate_images |
Generate social images via Nano Banana |
remix_latest_blog |
Full content remix of most recent post |
publish |
Post to social platform (requires MCP) |
Workflow
- Open https://frankx.ai/admin/content-studio on any device
- Click action buttons to queue tasks
- Run
/content-studio watchin Claude Code - Claude Code processes tasks automatically
- Dashboard refreshes to show new content
Architecture
┌────────────────────────┐ ┌────────────────────────┐
│ Content Studio │ │ Claude Code │
│ (Web Dashboard) │ │ (Desktop CLI) │
│ │ │ │
│ • Visual calendar │ │ • Process queue │
│ • Content cards │ │ • Generate content │
│ • Action buttons │ │ • Generate images │
│ • Platform filters │ │ • Commit to repo │
│ │ │ │
└──────────┬─────────────┘ └──────────┬─────────────┘
│ │
│ queue.json │
└──────────────────────────────┘
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 · 130 lines · 10 tokens per session scan A 6f8f71870baf
content-studio is a command published in the GitHub repository frankxai/agentic-creator-os (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 10 tokens to every session and 886 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
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.