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-pipelinegit clone --depth 1 https://github.com/SaigonXIII/evcWrote 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/saigonxiii/evc/content-pipeline)<a href="https://agentmods.dev/commands/saigonxiii/evc/content-pipeline"><img src="https://agentmods.dev/badge/commands/saigonxiii/evc/content-pipeline.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.00000 | $0.01360 |
| Opus 5 | $0.00000 | $0.00680 |
| Sonnet 5 | $0.00000 | $0.00272 |
| Haiku 4.5 | $0.00000 | $0.00136 |
Grade A, and why
content-pipeline 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 5d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Pipeline
Reference document showing the full Content Engine flow with human approval gates. This is not an executable command — it's a map of how content commands connect.
Trigger
User invokes /content-pipeline or says "show me the content flow", "how does the content engine work", "content pipeline diagram"
Pipeline Overview
CONTENT ENGINE — Full Pipeline
════════════════════════════════════════════════════════
WEEKLY CYCLE
────────────
/monday
|
| Phase 1: Gather (parallel, no approval)
| ├── /comms-scan ──> Triage inbound communications
| ├── /performance-review ──> Last week's metrics
| └── /intel-scan ──> Competitor + market intelligence
|
| [HUMAN GATE 1: Review Monday briefing]
|
| Phase 2: Plan
| └── /content-plan ──> Weekly brief + daily copy drafts
|
| [HUMAN GATE 2: Approve weekly plan]
|
v
DAILY PRODUCTION (repeat for each day)
──────────────────────────────────────
/content [day]
|
| 1. Load day brief from weekly plan
| 2. Load brand/canon-rules.json
| 3. Load content-engine/memory/lessons.md
| 4. Produce copy
| 5. Run /stop-slop (remove AI patterns)
|
| [HUMAN GATE 3: Review produced copy]
|
v
/content-qa
|
| Checks:
| ├── Canon compliance (banned phrases, required language)
| ├── Brand voice (tone, USP alignment)
| ├── /compliance-check (jurisdiction rules, disclaimers)
| ├── Character limits (platform-specific)
| └── Source traceability (every claim cited)
|
| Result: PASS or FAIL with specific violations
|
├── PASS ──> /post-today ──> Finalize + prepare for publishing
| |
| | [HUMAN GATE 4: Final approval before posting]
| |
| v
| Post to platform (manual or via API)
|
└── FAIL ──> Fix violations
|
v
Re-run /content-qa (loop until PASS)
|
v
/lesson-capture (auto-capture failure pattern)
BATCH MODE
──────────
/content-week
|
| Runs /content + /content-qa for each day in sequence
| Stops at first FAIL for human review
| Resumes after fix
|
v
WEEKLY CLOSE
────────────
/friday
|
| Phase 1: Review (parallel)
| ├── /performance-review ──> This week's metrics
| └── /weekly-digest ──> Team progress
|
| [HUMAN GATE 5: Review + correct before closing]
|
| Phase 2: Close out
| ├── Update project management (flag overdue)
| ├── Update memory (learning-log, visual-log)
| ├── /lesson-capture (capture week's learnings)
| └── /save-session (preserve state)
|
v
Next Monday: cycle repeats
════════════════════════════════════════════════════════
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.
- 5d ago First seen · 176 lines · 0 tokens per session scan A f1a0391cc78d
content-pipeline 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,360 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.
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.
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.