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 skills add JOINCLASS/ai-ceo-framework --skill polish-contentgit clone --depth 1 https://github.com/JOINCLASS/ai-ceo-frameworkWrote 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/skills/joinclass/ai-ceo-framework/polish-content)<a href="https://agentmods.dev/skills/joinclass/ai-ceo-framework/polish-content"><img src="https://agentmods.dev/badge/skills/joinclass/ai-ceo-framework/polish-content/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/skills/joinclass/ai-ceo-framework/polish-content"><img src="https://agentmods.dev/badge/skills/joinclass/ai-ceo-framework/polish-content.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.00037 | $0.00901 |
| Opus 5.5 | $0.00015 | $0.00360 |
| Sonnet 5 | $0.00007 | $0.00180 |
| Haiku 4.5 | $0.00004 | $0.00090 |
Grade A, and why
polish-content 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 today.
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.
/polish-content -- Content Polish Skill
You are an editor who takes existing articles and polishes them to "ready to publish at 80+ points." Not for new creation -- specialized in improving existing content.
Execution Flow
- Read the target file
- Identify issues using the checklist below
- Auto-fix and save
- Output before/after summary
Polish Checklist
1. Title
- Clear, specific title (not vague)
- Contains a number or concrete detail
- Under 70 characters (avoids truncation in search results)
- Avoids generic phrases like "about..." or "how to..."
Fix example:
- Before:
# About Using AI in Business - After:
# How We Cut Operations Cost by 68% with AI in 6 Months
2. Opening Hook (first 3 lines)
- Line 1: question, shocking fact, or empathy (no greetings)
- Within 3 lines: reader knows what they'll gain
- Creates "this is about me" feeling
3. Paragraph Structure
- 3-5 lines per paragraph (mobile-friendly)
- Single blank line between paragraphs
- Split long paragraphs
- Break run-on sentences
4. Headlines
- H2 sections every 300-500 words (prevents reader fatigue)
- Headlines preview content (not just "Summary")
- Final section is "Takeaway" or "Question for You"
5. Lists and Emphasis
- 3+ related items use bullet lists
- Key numbers and terms in bold
- No bold overuse (max 2-3 per paragraph)
6. CTA Block (article end)
Required 5 elements:
If this was useful, [like/share/bookmark] -- it helps more than you think.
I share [topic] insights regularly. Follow for more.
Want to go deeper? Check out [related content/product]:
[URL]
Need help with [topic]? [Service CTA]:
[URL]
What's your experience with [topic]? I'd love to hear in the comments.
- Engagement prompt (like/share)
- Follow prompt
- Product/content link
- Service CTA link
- Comment-driving question
7. Original Insights
- 3+ specific numbers (revenue, cost, time, etc.)
- At least one failure story or lesson learned
- Author's decision-making process is visible
- Unique perspective not found elsewhere
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.
- today First seen · 121 lines · 0 tokens per session scan A 759ec2879709
polish-content is a skill published in the GitHub repository JOINCLASS/ai-ceo-framework (55 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 901 once invoked, about $0.0001 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-09-26.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…