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 agentmods add skills/cwinvestments/memstack/blog-postnpx skills add cwinvestments/memstack --skill blog-postgit clone --depth 1 https://github.com/cwinvestments/memstackWhat 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 | $0.00069 | $0.02563 |
| Opus 5 | $0.00034 | $0.01282 |
| Sonnet 5 | $0.00014 | $0.00513 |
| Haiku 4.5 | $0.00007 | $0.00256 |
Grade A, and why
memstack-content-blog-post 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 3d 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
✍️ Blog Post — Writing SEO-optimized blog post...
Produces a complete, publish-ready blog post with SEO metadata, structured sections, readability optimization, and internal linking suggestions.
Activation
When this skill activates, output:
✍️ Blog Post — Gathering topic and audience details...
Then execute the protocol below.
| Context | Status |
|---|---|
| User says "write blog post" or "blog post about" | ACTIVE |
| User says "write article" or "create blog" or "write post" | ACTIVE |
| Creating long-form content for a website or publication | ACTIVE |
| Writing landing page copy (short-form, conversion-focused) | DORMANT — use landing-page-copy |
| Writing email content | DORMANT — use email-sequence |
| Writing social media posts | DORMANT |
Anti-patterns
| Trap | Reality Check |
|---|---|
| "Write about everything related to the topic" | Focus on one angle. Broad posts rank for nothing. Narrow posts rank for one keyword. |
| "The intro should provide context" | The intro should hook. Context bores. Open with a bold claim, stat, or question. |
| "Longer is better for SEO" | Comprehensive beats long. 1,500 focused words outrank 3,000 padded words. |
| "Stuff the keyword everywhere" | Use the keyword naturally 3-5 times. Search engines penalize stuffing. Readers hate it. |
| "Anyone who finds it will read it" | You have 3 seconds. If the title and intro don't hook them, the rest doesn't matter. |
Protocol
Step 1: Gather Topic Details
If the user hasn't provided details, ask:
I need a few details for the blog post:
- Topic — what's this post about?
- Target audience — who are you writing for? (developers, business owners, beginners, etc.)
- Target keyword — what search term should this rank for?
- Tone — casual/conversational, professional, technical, inspirational?
- Desired length — short (800 words), standard (1,200-1,500), long-form (2,000+)?
If the user provides partial info, infer what you can and ask only for what's missing.
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.
- 3d ago First seen · 281 lines · 69 tokens per session scan A 134d77bc37c7
memstack-content-blog-post is a skill published in the GitHub repository cwinvestments/memstack (417 stars, last pushed 6d ago), licensed MIT. It adds 69 tokens to every session and 2,563 once invoked, about $0.0003 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
plan-ceo-review
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when…
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, and create a PR. Use for an explicit /ship invocation or when the user requests the full ship, release, or deploy workflow. For an ordinary commit, push, or pull-request publishing request, use the built-in…
design-review
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use…
plan-eng-review
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when…
autoplan
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out. Use when…
retro
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively…