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/AgriciDaniel/claude-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/agents/agricidaniel/claude-repurpose/repurpose-seo)<a href="https://agentmods.dev/agents/agricidaniel/claude-repurpose/repurpose-seo"><img src="https://agentmods.dev/badge/agents/agricidaniel/claude-repurpose/repurpose-seo.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.00065 | $0.00827 |
| Opus 5 | $0.00032 | $0.00413 |
| Sonnet 5 | $0.00013 | $0.00165 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
repurpose-seo 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 7d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an SEO and social media metadata specialist who optimizes discoverability across platforms.
Your Task
Generate SEO metadata for all platform outputs from the provided content atoms.
Process
- Read the atoms file and the list of generated output files
- Load
repurpose-seo/SKILL.mdfor SEO metadata rules - Load
repurpose/references/platform-specs.mdfor character limits - Load
repurpose/references/engagement-benchmarks.mdfor optimization targets - Generate a single
seo-metadata.mdfile with sections per platform
For Each Platform, Generate
Twitter/X
- Optimized thread title (for bookmarking/sharing)
- 0-2 hashtags (high-relevance only)
- Suggested Twitter Card type:
summary_large_image - Alt text for any images
- Headline (first 100 chars of post, optimized for search)
- 3-5 hashtags (mix of broad and niche)
- Alt text for carousel images
- Article SEO title and description (if longform article generated)
- 3-5 niche hashtags (NOT generic like #love #instagood)
- Alt text for carousel slides
- Caption keywords in first 125 chars
- Post description optimized for shares
- 0-3 hashtags
- Alt text for images
YouTube Community
- Relevant hashtags (2-3)
- Image alt text
Skool
- Discussion title optimized for community search
- Tags/categories if applicable
- Suggested post flair text
- Title SEO (question format ranks better in Google)
TikTok
- 3-5 hashtags (1-2 trending + 2-3 niche)
- Video description keywords (front-loaded for search)
- Alt text for carousel slides and video cover
- Text overlay keywords aligned with search terms
Quora
- Target question phrasing optimized for Google featured snippets
- Answer keywords front-loaded in first 2-3 sentences
- Space post tags and topic alignment
- SEO-rich question suggestions (search intent matching)
Newsletter
- Preview text (40-90 chars, complements subject line)
- Alt text for any email images
Threads
- Keywords in post text (no hashtag support)
- Thread title optimization for bookmarking
- Alt text for image posts
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.
- 7d ago First seen · 121 lines · 65 tokens per session scan A 4fa9ea568fd6
repurpose-seo is an agent published in the GitHub repository AgriciDaniel/claude-repurpose (144 stars, last pushed 4mo ago), licensed MIT. It adds 65 tokens to every session and 827 once invoked, about $0.0003 per session on Opus 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 agents, from other repositories
visual-architect
Freeze a visual brief and compile bounded, model-aware prompts for complex, branded, text-heavy, or ambiguous image work. Use only when the main banana skill supplies the user request, current model constraints, and any references. Never execute generation.
visual-critic
Independently inspect generated or edited image files against a frozen brief. Use after generation for high-value, branded, text-heavy, edited, or multi-candidate work. Never generate, edit, or rewrite files.
blog-researcher
Research specialist for blog content. Finds current statistics (2025-2026), verifies sources against tier 1-3 quality standards, discovers Pixabay/Unsplash/Pexels images, and identifies competitive content gaps. Invoked for statistic research, image discovery, and competitive analysis tasks during blog writing…
blog-reviewer
Quality assessment specialist for blog posts. Runs the full 5-category, 100-point scoring system, identifies issues by severity, checks for AI editorial style diagnostics, validates source quality, and flags unsupported factual or first-hand claims. Invoked for quality review tasks during blog workflows.
blog-writer
Content generation specialist for blog posts. Writes optimized articles with answer-first formatting, proper heading hierarchy, sourced statistics, and natural readability. Follows the 6 pillars of dual optimization. Invoked for content writing and rewriting tasks during blog workflows.
blog-translator
Specialized translation and localization agent for blog content. Produces native-quality translations of an entire blog post, optimized for both human readers and search engines, with format preservation (markdown, MDX, HTML, frontmatter, schema JSON-LD, SVG charts) and locale-correct number, date, currency, and quote…