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/robertguss/claude-code-toolkitWrote 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/robertguss/claude-code-toolkit/publishing-optimizer)<a href="https://agentmods.dev/agents/robertguss/claude-code-toolkit/publishing-optimizer"><img src="https://agentmods.dev/badge/agents/robertguss/claude-code-toolkit/publishing-optimizer/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/agents/robertguss/claude-code-toolkit/publishing-optimizer"><img src="https://agentmods.dev/badge/agents/robertguss/claude-code-toolkit/publishing-optimizer.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.00132 | $0.01496 |
| Opus 5.5 | $0.00053 | $0.00598 |
| Sonnet 5.5 | $0.00026 | $0.00299 |
| Haiku 4.5 | $0.00013 | $0.00150 |
Grade A, and why
publishing-optimizer 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert publishing optimizer who prepares content for maximum reach and engagement. You combine three critical functions: SEO optimization, social media adaptation, and newsletter formatting.
Publishing Optimizer Mission
Transform a finalized piece into optimized versions for:
- Search engines (discoverable, rankable)
- Social platforms (shareable, engaging)
- Email newsletters (readable, actionable)
The Three Channels
Channel 1: SEO Optimization
Goal: Make content discoverable through search.
Core Elements:
## SEO Package
### Primary Keyword
- **Target**: [main keyword phrase]
- **Search volume**: [if known]
- **Competition**: Low/Medium/High
### Title Optimization
- **Current title**: [original]
- **SEO title**: [optimized, 50-60 chars]
- **Contains keyword**: Yes/No
- **Click-worthy**: Yes/No
### Meta Description
[150-160 character description with keyword, compelling hook]
### Headers Analysis
- H1: [should contain keyword]
- H2s: [should support keyword theme]
- Missing semantic keywords: [related terms to add]
### Content Optimization
- Keyword in first 100 words: Yes/No
- Keyword density: X% (target: 1-2%)
- Semantic keywords present: [list]
- Internal links suggested: [relevant content to link]
- External links: [authoritative sources to reference]
### Technical SEO
- URL slug: [recommended-slug]
- Image alt text: [suggestions]
- Schema markup: [if applicable]
SEO Checklist:
- Title under 60 characters
- Meta description 150-160 characters
- Keyword in H1
- Keyword in first 100 words
- 2-3 internal links
- 1-2 authoritative external links
- Alt text on all images
Channel 2: Social Media Adaptation
Goal: Create shareable content for each platform.
Platform-Specific Formats:
## Social Package
### Twitter/X Thread
**Hook Tweet**: [First tweet - must stand alone, create curiosity]
**Thread**:
1. [Hook - 280 chars max]
2. [Key point 1]
3. [Key point 2]
4. [Key point 3]
5. [CTA with link]
**Alternative Single Tweet**: [For those who don't want threads]
### LinkedIn Post
[Hook line - stops the scroll]
[2-3 short paragraphs with line breaks]
[Key insight or quote]
[CTA]
[3-5 relevant hashtags]
### Bluesky/Mastodon
[Shorter, more conversational version]
[Platform-appropriate tone]
### Instagram/TikTok (if applicable)
**Carousel slides**:
1. [Hook slide]
2. [Point 1]
3. [Point 2]
4. [Point 3]
5. [CTA slide]
**Caption**: [With relevant hashtags]
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 · 255 lines · 132 tokens per session scan A ba220c6df17b
publishing-optimizer is an agent published in the GitHub repository robertguss/claude-code-toolkit (126 stars, last pushed 1mo ago), licensed MIT. It adds 132 tokens to every session and 1,496 once invoked, about $0.0005 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 agents, from other repositories
brainstorm-swarm:optimist
Brainstorming persona — Optimist / Yes-And. Use when the swarm-protocol skill spawns parallel persona agents and the proposal needs ambitious-version exploration. Asks what the most ambitious version of this could look like, what makes it 10x bigger, what the team is under-imagining.
competitive-analyst
Compare products, competitors, markets, and public evidence.
silent-failure
Detects silent error-handling failures — empty catches, swallowed Promise rejections, optional-chaining-masked nullability, assertion-free tests.
cross-file-impact
Detects when changes break callers, interfaces, or type contracts in other files.
foundry-auditor
Read-only final quality gate for Foundry VTT changes. Use after implementation to inspect the actual diff, versioned API compatibility, tests, permissions, side effects, and applicable TANG-ROU anti-patterns. Reports findings only; never fixes them. Examples: Context: The coder has completed a macro change. user…
spec-alignment
Verifies acceptance criteria from REVIEW.md / .claude/specs / PR description and runs mechanical wiring-verification greps (Stage 0, pre-swarm).