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/f-amine/vibe-stack/blog-writernpx skills add f-amine/vibe-stack --skill blog-writergit clone --depth 1 https://github.com/f-amine/vibe-stackWrote 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/f-amine/vibe-stack/blog-writer)<a href="https://agentmods.dev/skills/f-amine/vibe-stack/blog-writer"><img src="https://agentmods.dev/badge/skills/f-amine/vibe-stack/blog-writer.svg" alt="Measured on agentmods" 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 | $0.00196 | $0.05894 |
| Opus 5 | $0.00098 | $0.02947 |
| Sonnet 5 | $0.00039 | $0.01179 |
| Haiku 4.5 | $0.00020 | $0.00589 |
Grade C, and why
blog-writer scanned grade C with 1 finding 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 today.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
2. Delete the stale image files: `rm -rf apps/marketing/public/blog/<slug>/` (the producer is idempotent and will regenerate). Or rename the directory to keep the originals. How it starts
The opening of the file, as written. The whole thing — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are coordinating a small swarm to ship one production-quality long-form blog post for vibestack's marketing journal. The output lands as a draft MDX file in apps/marketing/content/blog/, ready for human review.
Each post: 15-20 minute read = 3500-5000 words, with 4-8 inline images placed at natural reading breakpoints (not just a cover), full SEO metadata, internal links to vibestack surfaces where natural, and copy that earns the reader's time without being a thinly-veiled product ad.
Phase 0 — Brief
Ask the user at most two clarifying questions in one round, only if their request is ambiguous. Otherwise proceed silently from a sensible inference.
Required inputs you must resolve before launching the swarm:
- Topic — short title or theme. May be product-adjacent ("deploying with Dokploy", "Better Auth passkeys") or pure domain content ("Postgres connection pooling in 2026", "what AI-search engines reward in 2026"). The latter is encouraged — it builds topical authority without sounding like an ad.
- Audience lane —
developer(eng on Hacker News / Reddit / Lobsters; technical depth, code snippets, opinionated takes) orfounder(indie hackers / vibe-coders; concrete decisions, money implications, no jargon walls) ormixed. - Angle (optional) — the take. If the user said "write about X", invent the angle and surface it in your one-question round: "Going to angle this as 'X: the underrated reason it's faster than Y'. OK or counter?"
If the user just types /blog-writer with no args, ask:
"Topic, audience (developer / founder / mixed), and any specific angle you want? I'll pick a default angle if you skip it."
After one round, infer the rest and proceed.
Phase 1 — Spawn the swarm
There are five worker agents, run in three stages (not all parallel). Each agent's prompt is self-contained; they cannot see this session.
Researcher → Writer → ( SEO Editor + Image Prompt Architect ) → Image Producer → Publisher
solo solo parallel pair solo you
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.
- today First seen · 285 lines · 196 tokens per session scan C 3a167fa7af3e
blog-writer is a skill published in the GitHub repository f-amine/vibe-stack (21 stars, last pushed 2mo ago), licensed MIT. It adds 196 tokens to every session and 5,894 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
openspec-sync-specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
scaffold-project
Scaffold a new app, API, backend, fullstack project, monorepo, or starter with Better-T-Stack — including new projects built on a specific framework like Hono, Express, Fastify, Elysia, Next.js, TanStack Router/Start, Nuxt, Svelte, Solid, Astro, or React Native (native-bare, native-uniwind, native-unistyles). Use…
add-to-project
Add addons or features (PWA, Tauri, Starlight/Fumadocs docs, Biome/Oxlint, Husky/Lefthook, Turborepo/Nx, the MCP addon, etc.) to an existing Better-T-Stack project. Use when the user wants to extend, enhance, or add tooling to a project that was created with Better-T-Stack.