Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/SaigonXIII/evcnpx agentmods add commands/saigonxiii/evc/repurposeWrote 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/repurpose)<a href="https://agentmods.dev/commands/saigonxiii/evc/repurpose"><img src="https://agentmods.dev/badge/commands/saigonxiii/evc/repurpose/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/repurpose"><img src="https://agentmods.dev/badge/commands/saigonxiii/evc/repurpose.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.00056 | $0.03233 |
| Opus 5.5 | $0.00022 | $0.01293 |
| Sonnet 5.5 | $0.00011 | $0.00647 |
| Haiku 4.5 | $0.00006 | $0.00323 |
Grade A, and why
repurpose 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 — 355 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repurpose
Take one long-form piece and generate a full multi-channel content pack from it. Extracts the thesis, supporting points, quotes, stats, and CTA; drafts native formats for each channel; runs QA on each; and stages everything for side-by-side review.
Usage
/project:repurpose [slug] # blog (default source type)
/project:repurpose blog [slug]
/project:repurpose research [slug]
/project:repurpose report w15
Source Types
| Type | Input path |
|---|---|
blog (default) |
{{CONTENT_OUTPUT_DIR}}/blog/[slug]/copy.html + metadata.json + qa-report.md |
research |
{{CONTENT_OUTPUT_DIR}}/research/[slug]/report.md |
report |
{{CONTENT_OUTPUT_DIR}}/reports/[slug]/weekly-report.md |
Prerequisites
For blog source:
copy.htmlexists and has been through/blog-qawith verdict = READYmetadata.jsonpresent
For research source:
report.mdexists- At least one cited source present
For report source:
- Weekly report file exists
- Note: weekly reports are often internal —
/repurpose reportproduces LinkedIn + internal Slack formats only, not public X content
Steps
1. Gate Check
Read the source file(s). If they don't exist or (for blog) the QA verdict is not READY, stop with a clear message:
Source not READY. Blog QA verdict: NOT READY. Fix the issues in qa-report.md and re-run /blog-qa before repurposing.
2. Load Canon + Mode
- Read
{{CANON_DIR}}/canon-rules.json— brand voice, banned phrases, USPs - Load content-mode context — X character limits, link placement rules, no hashtags
- Read
{{CONTENT_ENGINE_DIR}}/memory/learning-log.mdif present — use winning patterns from past performance
3. Extract Key Elements
Read the source and extract what's actually there — never invent an element the piece doesn't contain:
- Thesis — the one-sentence claim
- Supporting points — the strongest arguments or data
- Pull quotes — verbatim lines strong enough to stand alone (if present)
- Hero stat — the most compelling number, with source (if present)
- Contrarian take — where the piece disagrees with conventional wisdom (only if it genuinely does)
- CTA — what should the reader do next?
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 · 355 lines · 56 tokens per session scan A fa8f2a8a26c5
repurpose is a command published in the GitHub repository SaigonXIII/evc (59 stars, last pushed 4mo ago), licensed MIT. It adds 56 tokens to every session and 3,233 once invoked, about $0.0002 per session on Opus 5.5. 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.
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.
review-content
Review content for brand alignment, lead placement, bio consistency, and proof points.