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 Notysoty/openagentskills --skill tech-blog-writergit clone --depth 1 https://github.com/Notysoty/openagentskillsWrote 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/notysoty/openagentskills/tech-blog-writer)<a href="https://agentmods.dev/skills/notysoty/openagentskills/tech-blog-writer"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/tech-blog-writer/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/notysoty/openagentskills/tech-blog-writer"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/tech-blog-writer.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.00017 | $0.01352 |
| Opus 5 | $0.00009 | $0.00676 |
| Sonnet 5 | $0.00003 | $0.00270 |
| Haiku 4.5 | $0.00002 | $0.00135 |
Grade A, and why
Technical Blog Post Writer 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 10d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Blog Post Writer
What this skill does
This skill directs the agent to write a complete technical blog post on a given topic — from a strong hook through to a practical conclusion — targeting a developer audience. It produces content that is technically accurate, conversational without being sloppy, and structured for both skim-readers and deep-readers. It also outputs an SEO title and meta description.
Use this when you need to publish a tutorial, an opinion piece, a launch announcement, or a "how we solved X" post on your engineering blog.
How to use
Claude Code / Antigravity
Copy this file to .agents/skills/tech-blog-writer/SKILL.md in your project root.
Then ask:
- "Write a blog post about how we migrated from REST to GraphQL using the Technical Blog Post Writer skill."
- "Use the Technical Blog Post Writer skill to write a tutorial on using React Query for server state management."
Provide:
- The topic or title idea
- The target audience (junior devs, senior backend engineers, general developer audience, etc.)
- The tone (opinionated/personal vs neutral/tutorial-style)
- Any key points, code snippets, or conclusions you want included
- Target length if you have a preference (default: 800-1200 words)
Cursor / Codex
Paste the instructions below into your session along with your topic brief.
The Prompt / Instructions for the Agent
When asked to write a technical blog post, follow these steps:
1. Plan before writing
Before drafting, identify:
- The problem the post addresses (developers reading this have this pain point)
- The insight or solution the post delivers
- The reader's takeaway — what can they do differently after reading?
- The assumed skill level — calibrate vocabulary and explanation depth accordingly
2. Structure the post
Every post must follow this structure:
Hook (first 2-3 sentences) Open with a relatable scenario, a surprising stat, or a bold claim. Do NOT open with "In this post, I will...". Do NOT open with a definition ("Docker is a containerization platform..."). Make the reader feel the problem before you name it.
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.
- 10d ago First seen · 150 lines · 17 tokens per session scan A 4c084949b36d
Technical Blog Post Writer is a skill published in the GitHub repository Notysoty/openagentskills (9 stars, last pushed 27d ago), licensed MIT. It adds 17 tokens to every session and 1,352 once invoked, about $0.0001 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-31.
Other skills, from other repositories
goose-graphics-create-style
End-to-end skill that turns a single reference image into a published Gooseworks style — analyzes the image, drafts the slim style spec, renders a hero example plus 2-3 additional formats via Playwright, writes the gooseworks-style.json manifest, and publishes via npx gooseworks styles publish so other agents can…
content-brief-factory
Generate detailed, differentiated content briefs at scale. Each brief includes SERP analysis, competing page breakdown, unique angles from real customer language (reviews, Reddit), internal linking plan, and SERP feature targets. Batch mode produces 10-50 briefs in one run. Crushes generic "keyword density" briefs…
goose-graphics-create-format
Creates a new graphics format spec (custom canvas dimensions + content rules) and publishes it to the Gooseworks library so any agent can render against it. Use when the existing community formats (carousel, story, infographic, slides, poster, chart, tweet, plus community additions) don't fit the user's canvas — e.g.…
generate-voice-guide
Generate a personal voice guide for X (Twitter) and/or LinkedIn by scanning a user's past posts and iteratively refining with sample-and-feedback loops. Produces a structured markdown voice guide that sibling skills (create-x-content, create-linkedin-content) consume to draft in-voice posts. Different from…
help-center-article-generator
Take support ticket clusters, FAQ patterns, product documentation, or feature specs and generate structured help center articles with step-by-step instructions, screenshot placeholders, troubleshooting sections, and related article links. Batch mode generates multiple articles from a ticket export. Pure reasoning…
create-linkedin-content
Draft voice-tuned LinkedIn post variants from a free-form brief. Reads a personal voice guide (generated via generate-voice-guide), produces 2–5 variants with distinct framings, applies LinkedIn-specific defaults (arrow bullets, "why this matters" beat, 150–500 words), and self-checks against the voice guide's banned…