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/post-todaygit 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/post-today)<a href="https://agentmods.dev/commands/saigonxiii/evc/post-today"><img src="https://agentmods.dev/badge/commands/saigonxiii/evc/post-today.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 | $0.00000 | $0.00754 |
| Opus 5 | $0.00000 | $0.00377 |
| Sonnet 5 | $0.00000 | $0.00151 |
| Haiku 4.5 | $0.00000 | $0.00075 |
Grade A, and why
post-today 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 4d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post Today
Post today's approved content to X, auto-reply with {{WEBSITE_URL}} link, and stage crosspost drafts.
Trigger
User invokes /post-today or says "post it", "publish today", "send the post", "go live"
Prerequisites
- Today's X copy must exist at
content-engine/output/[week]/[day]/x-copy.md - Content must have passed
/content-qa(check for QA report or run it now) - Banner must exist at
content-engine/output/[week]/[day]/banner.png(or video.mp4)
If prerequisites aren't met, tell the user what's missing and stop.
Steps
1. Load today's content
Detect today's day name. Read the X copy, banner path, and any LinkedIn copy from the output folder.
Run /content-qa if no QA report exists for today. Block on FAIL.
2. Final confirmation
POSTING TO X
════════════════════════════════════════
Copy ([char count]/280):
[the post text]
Media: [banner.png / video.mp4]
════════════════════════════════════════
Post now? (yes/edit/cancel)
3. Post to X
Post the approved copy to X using whichever channel the user has wired:
- If an X/Twitter MCP is installed: call its post tool with the copy text and media path.
- Otherwise: present the copy + media in a final confirmation block and ask the user to post it manually from their X client, then paste the resulting tweet URL back.
Capture the tweet ID from the returned URL — you need it for Step 4 and for /reply-monitor.
4. Auto-reply with link
Wait 10 seconds, then reply to the posted tweet with {{WEBSITE_URL}}:
- MCP path: call the post tool with
reply_to=<tweet_id>and body{{WEBSITE_URL}}. - Manual path: prompt the user to reply with the link and confirm once done.
5. Stage crosspost drafts
If LinkedIn copy exists in the output folder, present it:
CROSSPOST STAGED
════════════════════════════════════════
LinkedIn ([char count]/3000):
[linkedin copy]
Post to LinkedIn manually in 30-60 min.
════════════════════════════════════════
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.
- 4d ago First seen · 103 lines · 0 tokens per session scan A 68748231c15e
post-today 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 754 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.