What is content-week?

A batch workflow that creates the week's visual content after the written content has been approved. It builds banner layouts, renders videos, and exports image files such as PNGs.

Use it to turn an approved weekly brief into ready-to-post banners, video renders, and exported image files.

It avoids producing each week's visual assets one at a time and prevents unapproved copy from moving into production.

content-week — Command by SaigonXIII

Install

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.

agentmods

npx agentmods add commands/saigonxiii/evc/content-week

Clone the repo

git clone --depth 1 https://github.com/SaigonXIII/evc

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,505 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00000	$0.01505
Opus 5	$0.00000	$0.00753
Sonnet 5	$0.00000	$0.00301
Haiku 4.5	$0.00000	$0.00151

Measured 2d ago against content hash d9837374c909, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

content-week 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 2d 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.

_templates/commands/content-week.md · 154 lines

How it starts

The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Content Week

Batch-produce all visual assets for the week's approved content. Builds banners, renders videos, exports PNGs. No manual steps after this — everything comes out ready to post.

Trigger

User invokes /content-week or says "approved", "produce it", "build the assets", "batch produce"

Prerequisites

A weekly brief must exist with approved copy in content-engine/output/[week]/*/x-copy.md
The review dashboard at content-engine/output/[week]/dashboard.html should have been reviewed
If copy hasn't been approved, ask the user to review the dashboard first

Steps

1. Load Approved Copy

Read all x-copy.md files from content-engine/output/[week]/*/ to get:

The approved X copy for each day
Visual direction notes
Whether a video is needed (Wednesday)

2. Build Banner Templates

For each day that needs a static banner:

Create an HTML banner in the appropriate template style (from visual direction notes)
Use the social template system at brand/templates/social/templates/
Apply the headline, key stat, or partner screenshots as specified
Save to content-engine/output/[week]/[day]/banner.html

3. Export Banner PNGs

For each banner HTML:

Run node brand/templates/social/export.js --template [path] --platform x
Or use Puppeteer directly to screenshot at 2x (1200x675 for X)
Save to content-engine/output/[week]/[day]/banner.png

4. Build Video Compositions (if any)

For days that specify video (typically Wednesday):

Create a Remotion composition in the video project's src/clips/ directory
Use existing components from the component library
Register in Root.tsx
Render: npx remotion render src/index.ts [CompId] ../content-engine/output/[week]/[day]/video.mp4

5. Build LinkedIn Banners (if any)

For days with LinkedIn copy, export a LinkedIn-sized variant:

1200x627 dimensions
Save to content-engine/output/[week]/[day]/linkedin-banner.png

6. Copy QA Gate (MANDATORY — uses /content-qa pipeline)

Read the full file on GitHub · 154 lines

Changes

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.

2d ago First seen · 154 lines · 0 tokens per session scan A d9837374c909

Subscribe to this mod's changes

content-week 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 1,505 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.

Productivity Writing and docs agent-workspace ai-marketing claude-code content-engine marketing marketing-automation

content-week

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Content Week

Trigger

Prerequisites

Steps

1. Load Approved Copy

2. Build Banner Templates

3. Export Banner PNGs

4. Build Video Compositions (if any)

5. Build LinkedIn Banners (if any)

6. Copy QA Gate (MANDATORY — uses /content-qa pipeline)

What this file has done since we first saw it

Other commands, from other repositories

review-tool

setup

review-content

voice-check

content-status

draft-blog