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-update)<a href="https://agentmods.dev/commands/frankxai/agentic-creator-os/plan-update"><img src="https://agentmods.dev/badge/commands/frankxai/agentic-creator-os/plan-update/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-update"><img src="https://agentmods.dev/badge/commands/frankxai/agentic-creator-os/plan-update.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.00436 |
| Opus 5.5 | $0.00000 | $0.00174 |
| Sonnet 5.5 | $0.00000 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
plan-update 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-update — Update Plan Initiative
Update an initiative's status, progress, tasks, or add agent commentary.
Usage
/plan-update <slug> [action] [details]
Actions
| Action | Example | Description |
|---|---|---|
status |
/plan-update plan-system status shipped |
Change initiative status |
progress |
/plan-update content-velocity progress 45 |
Update progress percentage |
task |
/plan-update plan-system task ps-2 done |
Mark a task complete |
comment |
/plan-update plan-system comment "Hub page deployed" |
Add agent commentary |
priority |
/plan-update youtube-launch priority high |
Change priority level |
Execution Steps
- Read
lib/plan/initiatives.tsto find the initiative by slug - Apply the requested change using Edit tool
- Update
lastUpdatedto today's date - If status changed to
shipped, add a celebration comment from the lead agent - Generate a VECTOR agent feed entry in
data/feed-entries.json - Run
npx tsc --noEmitto verify no TypeScript errors - Report what changed
Valid Status Values
idea→planned→in-progress→shipped→evolved
Valid Priority Values
critical,high,medium,low
Feed Entry Template
When generating a feed entry for status changes:
{
"id": "feed-plan-NNN",
"agent": "VECTOR",
"agentRole": "Direction & Planning",
"timestamp": "<ISO timestamp>",
"type": "status",
"content": "<Initiative title> moved to <new status>. <Brief context>.",
"tags": ["plan", "<track>", "<status>"],
"linkedContent": "/plan/<slug>",
"sentiment": "methodical"
}
$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 · 55 lines · 0 tokens per session scan A c99a4afaec88
plan-update 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 436 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
business-model
Explore business models using Lean Canvas, Business Model Canvas, Startup Canvas, or Value Proposition frameworks.
brainstorm
Brainstorm product ideas or experiments from PM, Designer, and Engineer perspectives — for existing or new products.
discover
Run a full product discovery cycle — from ideation through assumption mapping to experiment design.
setup-metrics
Design a product metrics dashboard with North Star metric, input metrics, health metrics, and alert thresholds.
triage-requests
Analyze, categorize, and prioritize a batch of feature requests from customers or stakeholders.
pricing
Design a pricing strategy — models, competitive analysis, willingness-to-pay estimation, and pricing experiments.