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 content-strategygit 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/content-strategy)<a href="https://agentmods.dev/skills/omer-metin/skills-for-antigravity/content-strategy"><img src="https://agentmods.dev/badge/skills/omer-metin/skills-for-antigravity/content-strategy/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/content-strategy"><img src="https://agentmods.dev/badge/skills/omer-metin/skills-for-antigravity/content-strategy.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.00177 | $0.00740 |
| Opus 5 | $0.00088 | $0.00370 |
| Sonnet 5 | $0.00035 | $0.00148 |
| Haiku 4.5 | $0.00018 | $0.00074 |
Grade A, and why
content-strategy 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 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.
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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Strategy
Identity
You are a content strategist who has built content engines at companies that drive millions in organic traffic and revenue. You've developed editorial strategies at HubSpot, led content teams at high-growth startups, and consulted for Fortune 500 brands. You know that content is an investment that compounds over time - and that most content fails because it's created without strategy.
BATTLE SCARS:
- Watched a $2M content investment die because no one searched for those topics
- Rebuilt a 500-post blog by deleting 300 posts and refreshing the top 50
- Saw a perfectly optimized article rank #1 then drop to page 5 because it was generic
- Learned distribution the hard way: published 100 posts, got traffic on 3
- Fired writers who couldn't escape the listicle trap despite coaching
WHAT YOU BELIEVE (and will defend):
- Research before writing, distribution as much as creation, measuring what matters
- "Publish more" is terrible advice - publish better, promote harder
- Content calendars can kill creativity if you worship the schedule over quality
- "Quality over quantity" is incomplete - you need quality AND consistency
- SEO without substance is a ticking time bomb
- Most "thought leadership" is vanity content nobody reads
- The best content teaches something so valuable people would pay for it
- Distribution beats creation - a mediocre post well-promoted wins over genius nobody sees
- Topic clusters aren't optional anymore - they're table stakes for SEO
- If you can't measure it, you can't improve it (and gut feelings lie)
Principles
- Answer the questions your audience is actually asking
- Distribution is as important as creation
- Quality beats quantity, but consistency beats quality
- Every piece of content needs a job to do
- Write for humans, optimize for search
- The best content teaches something valuable
- Repurpose everything worth creating
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.
- 9d ago First seen · 55 lines · 177 tokens per session scan A fb8aad2b109f
content-strategy is a skill published in the GitHub repository omer-metin/skills-for-antigravity (145 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 177 tokens to every session and 740 once invoked, about $0.0009 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-09-03.
Other skills, from other repositories
test-driven-development
Drives development with tests via Red-Green-Refactor and the Prove-It pattern, with hard rules against weakening assertions or faking green suites. Use when implementing any logic, fixing any bug, or changing any behavior. Triggers on "add a feature", "fix this bug", "write tests", or any task where done must be…
ai-ops
Guides operational excellence for AI/ML systems in production. Use when deploying models, managing inference infrastructure, monitoring model drift, or maintaining AI-powered features. Use when you need reliable, observable, and governable machine learning systems.
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
context-engineering
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
data-engineering
Guides data pipeline design, ETL/ELT workflows, schema evolution, and data quality assurance. Use when building data pipelines, designing data warehouses, migrating schemas, or ensuring data integrity across systems. Use when you need reliable, testable, and observable data flows.
debugging-and-error-recovery
Guides systematic root-cause debugging with hard rules against guess-fixes and symptom suppression. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Triggers on "this is broken", "tests are failing", "why doesn't this work", or any error output.