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/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/crosspost)<a href="https://agentmods.dev/commands/saigonxiii/evc/crosspost"><img src="https://agentmods.dev/badge/commands/saigonxiii/evc/crosspost/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/saigonxiii/evc/crosspost"><img src="https://agentmods.dev/badge/commands/saigonxiii/evc/crosspost.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.00617 |
| Opus 5.5 | $0.00000 | $0.00247 |
| Sonnet 5.5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
crosspost 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Crosspost
Distribute content across X, LinkedIn, and Threads with platform-native adaptation.
Trigger
User invokes /crosspost or says "crosspost", "post everywhere", "share on all platforms", "distribute this"
Core Rules
- Never post identical content cross-platform. Each platform gets a native adaptation.
- X is primary. Post to X first (largest audience), then adapt for others.
- Respect platform conventions. Length, formatting, tone all differ.
- One idea per post. Split multi-idea content across posts.
- Canon guardrails apply. All content must follow brand canon and approved messaging.
Platform Specs
| Platform | Max Length | Link Handling | Hashtags | Tone |
|---|---|---|---|---|
| X | 280 chars | Counted in length | None (config.md) | Founder, direct, confident |
| 3000 chars | Not counted | 3-5 relevant | Professional, insight-led | |
| Threads | 500 chars | Separate attachment | None | Casual, conversational |
Steps
1. Get source content
Identify the anchor asset (blog, banner, announcement, weekly day content). Extract the core message.
2. Draft X version first
- Open with a hook, not a summary
- Cut to the core insight fast
- Keep under 280 chars
- Apply /stop-slop rules
- Include Audience, Key Message, Tone of Voice justification
3. Adapt for LinkedIn
- Strong first line (visible before "see more")
- Short paragraphs with line breaks
- Frame around lessons, results, or professional takeaways
- More explicit context than X
- 3-5 relevant hashtags
4. Adapt for Threads (optional)
- Conversational, casual tone
- Shorter than LinkedIn, less compressed than X
- Visual-first if possible
5. Present all versions
Show in a table:
| Platform | Draft | Chars |
|---|---|---|
| X | [draft] | [count] |
| [draft] | [count] | |
| Threads | [draft] | [count] |
6. Post approved versions
- X: post via an X/Twitter MCP tool if available, otherwise stage for manual posting
- LinkedIn: draft for manual posting (no first-party API flow)
- Threads: draft for manual posting (no first-party API flow)
- Stagger 30-60 min between platforms
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 · 80 lines · 0 tokens per session scan A 04dfe1ae217e
crosspost is a command published in the GitHub repository SaigonXIII/evc (59 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 617 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.