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/saigonxiii/evc/content-plangit clone --depth 1 https://github.com/SaigonXIII/evcWhat 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 | $0.00000 | $0.00957 |
| Opus 5 | $0.00000 | $0.00478 |
| Sonnet 5 | $0.00000 | $0.00191 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
content-plan 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 3d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Plan
Weekly content planning for {{COMPANY_NAME}}'s Monday-Friday social content. The brain of the content engine.
Trigger
User invokes /content-plan or asks to "plan this week's content", "build the content calendar", "what should we post"
Arguments
- Optional: week identifier (e.g.,
/content-plan W14). Defaults to next week.
Prerequisites
- Intel scan should have been run first (
/intel-scan). If no intel report exists for this week, note it and work from memory files. - Content review for last week should exist. If not, note it.
Steps
1. Gather Intelligence
Read all available inputs:
- Latest intel report:
content-engine/calendar/intel-*.md(most recent) - Last week's review:
content-engine/calendar/*-review.md(most recent) - Learning log:
content-engine/memory/learning-log.md - Visual log:
content-engine/memory/visual-log.md - Competitor watch:
content-engine/memory/competitor-watch.md - Asset library:
content-engine/memory/asset-library.md - Config:
content-engine/config.md - Audience segments:
content-engine/memory/audience-segments.md
2. Assess Narrative Arc
Read the past 2-4 weeks of briefs from content-engine/calendar/ to understand:
- What narratives have we been building?
- What topics have we covered recently (avoid repeating)?
- What's the natural next beat in the story we're telling?
- Are we balanced across audience segments?
3. Build the Weekly Brief
Create a brief with:
Context section:
- Key intel signals (top 3 from research)
- Last week's top performer and why
- Narrative position (what we're building from and toward)
5-Day Calendar: For each day (Monday-Friday), specify:
- Pillar (from config schedule)
- Primary audience segment (A/B/C/D from audience-segments.md)
- Headline concept (the core idea, not final copy)
- Visual direction (template, dark/light, stat-led/story-led, video/static)
- Canon source (which doc to pull messaging from)
- How it builds on previous posts (narrative threading)
- Platform format (X only, X + LinkedIn, video clip, thread)
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.
- 3d ago First seen · 102 lines · 0 tokens per session scan A 384f91ca9cfe
content-plan is a command published in the GitHub repository SaigonXIII/evc (56 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 957 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-08-30.
Other commands, from other repositories
review-tool
Research a tool or product for skill-gap, architecture, and verb-fit per the Anatomy framework.
setup
First-run setup — replace the fictional company and authors with yours.
review-content
Review content for brand alignment, lead placement, bio consistency, and proof points.
voice-check
Check a draft against the author's voice profile and flag deviations.
content-status
Scan all content directories and report status of drafts, ideas, and published content.
draft-blog
Scaffold a blog post with proper structure, voice, and frontmatter.