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 laurigates/claude-plugins --skill blog-post-writinggit clone --depth 1 https://github.com/laurigates/claude-pluginsWrote 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/laurigates/claude-plugins/blog-post-writing)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/blog-post-writing"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/blog-post-writing.svg" alt="Measured on agentmods" 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.00039 | $0.02122 |
| Opus 5 | $0.00019 | $0.01061 |
| Sonnet 5 | $0.00008 | $0.00424 |
| Haiku 4.5 | $0.00004 | $0.00212 |
Grade A, and why
blog-post-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 8d 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 — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blog Post Writing
Expert guidance for creating consistent, scannable blog posts about projects and technical work. Optimized for capturing work in progress and sharing accomplishments.
When to Use This Skill
| Use this skill when... | Use blog-post instead when... |
|---|---|
| You need the full style guide and post-type templates as reference | You want to create a blog post file now with guided prompts (/blog:post) |
| Auto-loading consistent voice/structure rules while drafting prose | You need git context and frontmatter auto-populated into a new post |
| Documenting which post type (quick-update / project-update / retrospective / tutorial / deep-dive) fits the situation | You already know the type and want the file scaffolded |
Core Expertise
- Low-friction capture: Quick entry formats that reduce blank-page anxiety
- Consistent structure: Predictable patterns for easy scanning later
- Multiple post types: From quick updates to detailed tutorials
- Project context: Automatic metadata for tracking work across projects
- Future-proof: Structure that supports later automation and publishing
When This Skill Activates
This skill activates when:
- User wants to write about work they've done
- User needs to document a project update
- User wants to create a devlog entry
- User requests a blog post or article about technical work
- User mentions "write up", "blog", "post", or "devlog"
Post Types
| Type | When to Use | Typical Length |
|---|---|---|
| Quick Update | Captured something small, daily log | 100-300 words |
| Project Update | Milestone, feature complete, notable progress | 300-800 words |
| Retrospective | Looking back at a project or time period | 500-1500 words |
| Tutorial | Teaching how to do something | 800-2000 words |
| Deep Dive | Explaining complex concepts or decisions | 1000-3000 words |
Universal Post Structure
Every post uses this metadata frontmatter:
---
title: <descriptive title>
date: YYYY-MM-DD
type: quick-update | project-update | retrospective | tutorial | deep-dive
project: <project-name>
tags: [tag1, tag2]
status: draft | published
---
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.
- 8d ago First seen · 411 lines · 39 tokens per session scan A 4e305b4761e3
blog-post-writing is a skill published in the GitHub repository laurigates/claude-plugins (58 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 2,122 once invoked, about $0.0002 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
extract-ssot
Deduplicate repeated markdown content, rule files, skill bodies, ADRs, docs, into a single named source of truth and migrate every call site to cite it by exact heading. Use when the same prose, literal, or concept appears (or is reworded) across files: 'DRY this prose', 'extract a shared rule', 'single source of…
feature-branch-pr-writing
Use this skill when the user asks to write, draft, create, or improve a PR description for a Shopware core repository PR — AND that PR targets a non-trunk feature branch (not trunk itself). Trigger phrases like "write a PR description", "draft the PR", "what should I put in the PR body". The skill detects the target…
ci-log-interpretation
Use this skill when reading or analyzing CI logs from a Shopware GitHub Actions workflow to figure out why a build failed — phrases like "why did CI fail", "what broke the build", "check the pipeline", "interpret these logs", "debug this red build" — or whenever raw run logs, job logs, or check annotations from a…
repo-activity
Scan all git repositories under /repos and report recent activity — last commit age, branch, uncommitted changes — in age-bucketed tables. Use when the user asks for a repo activity overview, "what have I been working on", portfolio status, or which repos are active/dormant.
a0-create-plugin
Create, extend, or modify Agent Zero plugins. Follows strict full-stack conventions (usr/plugins, plugin.yaml, Store Gating, AgentContext, plugin settings). Use for UI hooks, API handlers, lifecycle extensions, or plugin settings UI.
a0-contribute-plugin
Guide for publishing an Agent Zero plugin to the community Plugin Index (a0-plugins repo). Covers GitHub repo setup, index.yaml creation, CI validation rules, and PR submission. Use when the user wants to share, publish, submit, or contribute a plugin to the Plugin Hub so other Agent Zero users can find and install it.