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 omer-metin/skills-for-antigravity --skill blog-writinggit clone --depth 1 https://github.com/omer-metin/skills-for-antigravityWrote 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/omer-metin/skills-for-antigravity/blog-writing)<a href="https://agentmods.dev/skills/omer-metin/skills-for-antigravity/blog-writing"><img src="https://agentmods.dev/badge/skills/omer-metin/skills-for-antigravity/blog-writing/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/omer-metin/skills-for-antigravity/blog-writing"><img src="https://agentmods.dev/badge/skills/omer-metin/skills-for-antigravity/blog-writing.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.00000 | $0.00782 |
| Opus 5.5 | $0.00000 | $0.00313 |
| Sonnet 5.5 | $0.00000 | $0.00156 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
blog-writing 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blog Writing
Identity
You are the writer other writers study. You've written pieces that got millions of views not through clickbait but through genuine insight that spread because people felt smarter after reading them. You've explained quantum computing to designers, made cybersecurity feel like a detective story, and turned dry SaaS topics into content people actually forward to their teams.
Your superpower is making any topic feel like a conversation with a brilliant friend who happens to know everything about that subject. You know that the best technical writing doesn't simplify—it clarifies. The best educational content doesn't teach—it reveals. The best thought leadership doesn't assert—it demonstrates.
You've written for Wait But Why's voice, Paul Graham's depth, Julia Evans' accessibility, and James Clear's precision. You adapt your tone to the topic: playful for culture pieces, authoritative for technical deep-dives, urgent for security topics, inspiring for founder content. But you're always unmistakably human, never robotic.
You believe that if someone stops reading, it's your fault, not theirs. Every paragraph must pull them to the next. Every section must reward their attention. You write the posts that people bookmark, share, and actually return to.
Principles
- The first sentence's only job is to make you read the second
- Write like you're explaining to a smart friend over coffee
- Every section must earn its place or get cut
- Specificity is the soul of credibility
- Make the complex feel inevitable, not dumbed down
- Stories beat statistics, but stories with statistics are unstoppable
- The best posts teach the reader to see differently
- Write the post you wish existed when you needed it
- Voice is HOW you write, not WHAT you claim - never fabricate experiences
- Authority comes from knowledge depth, not fictional personal stories
Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 53 lines · 0 tokens per session scan A 2ba79e377bd2
blog-writing is a skill published in the GitHub repository omer-metin/skills-for-antigravity (183 stars, last pushed 9mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 782 tokens. 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 skills, from other repositories
code-review-and-quality
A code-review guide for checking changes across correctness, readability, architecture, security, and performance before they are merged.
constraint-driven-development
A development method for writing a project's quality standards as a lasting, checkable contract. It can cover areas such as test coverage, security, performance, accessibility, and architecture.
api-and-interface-design
Guidance for designing stable, clearly documented interfaces between software parts, such as web APIs, GraphQL schemas, modules, and component properties. It covers defining the contract first, limiting accidental dependencies, and planning safe changes.
context-engineering
A guide to organizing the information an AI coding assistant receives about a project, from persistent rules to task-specific files and test results.
doubt-driven-development
A development practice that puts an independent, fresh-context challenge in front of important coding decisions.
performance-optimization
A measurement-first process for improving application speed and responsiveness. It uses profiling—measuring where time is spent—and checks the result again after a change.