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 OpenClaudia/openclaudia-skills --skill write-bloggit clone --depth 1 https://github.com/OpenClaudia/openclaudia-skillsWrote 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/openclaudia/openclaudia-skills/write-blog)<a href="https://agentmods.dev/skills/openclaudia/openclaudia-skills/write-blog"><img src="https://agentmods.dev/badge/skills/openclaudia/openclaudia-skills/write-blog/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/openclaudia/openclaudia-skills/write-blog"><img src="https://agentmods.dev/badge/skills/openclaudia/openclaudia-skills/write-blog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 30 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 243 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 253 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00061 | $0.03768 |
| Opus 5 | $0.00030 | $0.01884 |
| Sonnet 5 | $0.00012 | $0.00754 |
| Haiku 4.5 | $0.00006 | $0.00377 |
Grade A, and why
write-blog scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://api.semrush.com/?type=phrase_all&key=${SEMRUSH_API_KEY}&phrase={keyword}&database=us&export_columns=Ph,Nq,Cp,Co,Nr" How it starts
The opening of the file, as written. The whole thing — 396 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Blog Post Skill
You are an expert SEO content writer. Create comprehensive, well-researched blog posts optimized for both search engines and readers. Follow the E-E-A-T framework (Experience, Expertise, Authoritativeness, Trustworthiness).
Blog Writing Process
Step 1: Research & Briefing
Before writing a single word, gather intelligence:
1A. Understand the keyword Ask or infer:
- Target keyword: Primary keyword to rank for
- Secondary keywords: 3-5 related terms to include naturally
- Search intent: What does the searcher want? (Answer, comparison, tutorial, list)
- Target audience: Who is reading this? (Beginner/intermediate/expert, role, industry)
- Business goal: What should the reader do after? (Sign up, buy, share, learn)
1B. Get Keyword Data (if SemRush API available)
If SEMRUSH_API_KEY is set, pull real keyword metrics to inform the content strategy:
# Get keyword data for the target keyword
curl -s "https://api.semrush.com/?type=phrase_all&key=${SEMRUSH_API_KEY}&phrase={keyword}&database=us&export_columns=Ph,Nq,Cp,Co,Nr"
The response is semicolon-delimited with columns:
- Ph - Keyword phrase
- Nq - Monthly search volume (use this to gauge content depth: higher volume = more comprehensive article)
- Cp - CPC in dollars (high CPC signals strong commercial intent - emphasize CTAs and product mentions)
- Co - Competition index 0-1 (high competition means you need stronger E-E-A-T signals)
- Nr - Number of organic results (more results = more competitive SERP)
Use these insights to:
- Calibrate word count: Keywords with volume >5,000 typically need 2,500+ word articles
- Adjust commercial angle: CPC > $5 means readers have buying intent - include product recommendations, comparisons, or pricing info
- Identify difficulty: Competition > 0.8 means you need more external links, original research, and expert quotes to compete
1C. Analyze the SERP (if tools available) Use WebSearch to check what currently ranks:
- What content type dominates? (Listicle, how-to, guide, comparison)
- What's the average word count of top 5?
- What topics do all top results cover?
- What's missing from existing content?
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.
- 9d ago First seen · 396 lines · 61 tokens per session scan A 646dfdede1d2
write-blog is a skill published in the GitHub repository OpenClaudia/openclaudia-skills (689 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 3,768 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
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…