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/plan-sync)<a href="https://agentmods.dev/commands/frankxai/agentic-creator-os/plan-sync"><img src="https://agentmods.dev/badge/commands/frankxai/agentic-creator-os/plan-sync/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/plan-sync"><img src="https://agentmods.dev/badge/commands/frankxai/agentic-creator-os/plan-sync.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.00380 |
| Opus 5.5 | $0.00000 | $0.00152 |
| Sonnet 5.5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
plan-sync 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.
What it actually says
/plan-sync — Sync Plan to Production
Sync all plan-related files to the production worktree and deploy.
What This Syncs
lib/plan/initiatives.ts → .worktrees/vercel-ui-ux/lib/plan/
app/plan/layout.tsx → .worktrees/vercel-ui-ux/app/plan/
app/plan/page.tsx → .worktrees/vercel-ui-ux/app/plan/
app/plan/[slug]/page.tsx → .worktrees/vercel-ui-ux/app/plan/[slug]/
app/plan/[slug]/PlanInitiativePage.tsx → .worktrees/vercel-ui-ux/app/plan/[slug]/
data/feed-entries.json → .worktrees/vercel-ui-ux/data/
Execution Steps
- Create directories in production worktree if they don't exist
- Copy all plan files to
.worktrees/vercel-ui-ux/ - Copy updated
data/feed-entries.jsonto production - Stage all changed files in production worktree
- Commit with message:
feat: Sync plan system updates - Push to production using WSL2 git token workaround
- Report deployment status
WSL2 Push Command
cd .worktrees/vercel-ui-ux
TOKEN=$(gh auth token) && git -c "http.https://github.com/.extraheader=Authorization: Basic $(echo -n "x-access-token:$TOKEN" | base64 --wrap=0)" -c credential.helper= push origin main
Verification
After push, verify at:
$ARGUMENTS
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 · 41 lines · 0 tokens per session scan A 02f8eadbcebb
plan-sync 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 380 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
sprint
Sprint lifecycle — plan a sprint, run a retrospective, or generate release notes.
changelog
Create engaging changelogs for recent merges to main branch.
release
Automate semantic versioning releases or scaffold release infrastructure.
versioning
Universal version file discovery and sync. Works with any project structure.
release-please-setup
Scaffold or migrate a repo onto release-please (config, manifest, release workflow) with optional tag-keyed deploy/publish templates.
sync-ecosystem
Detect API changes, sync satellite repos, and publish releases.