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 kostja94/marketing-skills --skill bloggit clone --depth 1 https://github.com/kostja94/marketing-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/kostja94/marketing-skills/blog)<a href="https://agentmods.dev/skills/kostja94/marketing-skills/blog"><img src="https://agentmods.dev/badge/skills/kostja94/marketing-skills/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/kostja94/marketing-skills/blog"><img src="https://agentmods.dev/badge/skills/kostja94/marketing-skills/blog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00086 | $0.01117 |
| Opus 5 | $0.00043 | $0.00558 |
| Sonnet 5 | $0.00017 | $0.00223 |
| Haiku 4.5 | $0.00009 | $0.00112 |
Grade A, and why
blog-page-generator 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 13d 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- blog-page-generator — 100% identical, 0 lines differ
- blog-page-generator — 100% identical, 0 lines differ
- blog-page-generator — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pages: Blog
Guides blog page structure, SEO, and content marketing best practices.
When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for topics, audience, and keywords.
Identify:
- Blog purpose: SEO traffic, thought leadership, product education
- Content mix: Pillar pages, cluster content, news
- Audience: Buyers, existing customers, developers
Best Practices
Blog Placement: Subdomain vs Subdirectory
| Option | Example | SEO / Use |
|---|---|---|
| Subdirectory | example.com/blog |
SEO weight flows to main domain; recommended for product blogs |
| Subdomain | blog.example.com |
Treated as separate entity; consider for distinct brands or technical isolation |
Choose based on SEO weight distribution, brand consistency, and technical architecture. See Alignify subdomain vs subdirectory guide for details.
Blog Index Page Structure
| Section | Purpose |
|---|---|
| Featured/Recent | Highlight newest or most important posts |
| Categories/Topics | Help users find by theme |
| Editor's Picks | Curate best content |
| Related posts | Per-article recommendations |
| Search | Help users find specific topics |
Content Strategy
- Topical authority: Topic clusters -> pillar page per core topic + 6-12 cluster articles
- Intent mapping: Transactional, problem-aware, informational
- EEAT signals: Author bios, Organization schema, citations, changelog
- Refresh > new: For established sites, updating existing content often outperforms publishing new posts; avoid changing only the date without substantive edits
- Quality > quantity: Fewer high-quality posts beat many mediocre ones; consider deleting, merging, or refreshing underperformers
- Topic focus: Avoid blindly expanding topics; dilution can hurt authority on core topics
- Conversion as north star: SEO KPIs should tie to leads, signups, or sales -> not just traffic
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.
- 13d ago First seen · 97 lines · 86 tokens per session scan A e6b5e9984231
blog-page-generator is a skill published in the GitHub repository kostja94/marketing-skills (967 stars, last pushed 3mo ago), licensed MIT. It adds 86 tokens to every session and 1,117 once invoked, about $0.0004 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-30.
Other skills, from other repositories
SEO Content Optimizer
Analyzes and rewrites content to maximize search engine visibility without sounding robotic.
cold-outbound-sequencer
Use when the user asks to "build a B2B cold-outbound sequence", "design reply-triage branching", "plan a domain warmup / sending throttle", or "make my outbound CAN-SPAM / opt-in compliant"; produces a multi-step outbound sequence with reply-triage branches (positive / objection / referral / not-now / opt-out), a…
inbox-placement-monitor
Use when the user asks to "track where my emails are actually landing after I send", "read my seed-list inbox vs spam vs promotions results", "trend my Gmail Postmaster / Microsoft SNDS reputation", or "did placement drop after my last send"; produces a per-provider inbox/spam/promotions placement read, a domain/IP…
newsletter-monetization-planner
Use when the user asks to "monetize my newsletter", "build a sponsorship rate card", or "model paid-subscription revenue"; produces a revenue model (paid tiers, ad/sponsorship inventory + CPM/flat rate card, referral/boost loops), a list-growth ↔ revenue projection, and honest-offer / disclosure checks for the SEND-D…
budget-optimizer
Use when the user asks to "allocate my influencer budget", "optimize spend across tiers", or "compare budget scenarios"; produces a tier/platform/content allocation table, ROI and CPM/CPE projections, scenario comparisons, and mid-campaign reallocation moves. Not for building the full campaign plan — use…
sales-enablement-kit
Use when the user asks to "build battle cards", "prep the sales team for launch", or "write the internal launch FAQ"; produces the internal enablement kit for a sales-led launch — battle cards vs each named alternative (where we win / where they win / trap questions, every fact traceable), a sales talk track derived…