blog.check_format

blog.check_format is a skill for Claude Code from gpsaggese/helpers. It costs 7 tokens per session (328 once invoked), scanned A, original, Apache-2.0.

A blog-format checker that scans Markdown blog files and compares them with the project's writing rules. It also checks for required sections such as a TL;DR.

In plain words
What is it for?
Use it to check blog drafts and published posts, report violations with file and line references, and choose which problems to fix.
Why use it?
It finds missing structure and rule violations before a blog is published, so you do not have to inspect every file manually.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; reads .claude/ paths.

Good fit Use it to check blog drafts and published posts, report violations with file and line references, and choose which problems to fix.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gpsaggese/helpers/blog.check_format
Install

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.

Any agent
npx skills add gpsaggese/helpers --skill blog.check_format
Clone the repo
git clone --depth 1 https://github.com/gpsaggese/helpers

Made for: Claude Code.

Wrote 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.

agentmods badge for blog.check_format

README.md
[![agentmods](https://agentmods.dev/badge/skills/gpsaggese/helpers/blog.check_format/github.svg)](https://agentmods.dev/skills/gpsaggese/helpers/blog.check_format)
Your own site
<a href="https://agentmods.dev/skills/gpsaggese/helpers/blog.check_format"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/blog.check_format/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.

agentmods 80×15 button for blog.check_format

Your own site · 80×15
<a href="https://agentmods.dev/skills/gpsaggese/helpers/blog.check_format"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/blog.check_format.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 328 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00007 $0.00328
Opus 5.5 $0.00003 $0.00131
Sonnet 5.5 $0.00001 $0.00066
Haiku 4.5 $0.00001 $0.00033

Measured yesterday against content hash 4f7b89e38f5a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

blog.check_format 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 yesterday.

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.

.claude/skills/blog.check_format/SKILL.md · 50 lines

What it actually says

Goal

  • Check that all the actual and the draft blogs have the correct format

Workflow

Find Files

  • Find all markdown files, both SKILL.md and <TOPIC>.rules.md
    > find website/docs/blog/posts -name "*.md"
    

Read Context

  • Read the rules in
    • .claude/skills/blog.rules.md
    • .claude/skills/markdown.rules.md
    • .claude/skills/text.rules.md

Check Rules

  • Apply all the rules below to each file and report violations

Check Front Matter

  • Follow # Blog Document Structure in .claude/skills/blog.rules.md

Check that Has a TL;DR

  • Follow # Blog Document Structure in .claude/skills/blog.rules.md

Check for Other Violations

  • Use .claude/skills/blog.rules.md to find clear violations
  • Report a violation only when confident about it

Report Violations

  • Report all violations in a file cfile using the format in .claude/skills/cfile.rules.md

Ask Users Whether to Fix the Problems

  • Print a list of problems with indices and ask the user which to fix

Verification

  • Confirm cfile lists concrete file and line references for each violation
  • Confirm each reported violation maps to a rule in .claude/skills/blog.rules.md
Changes

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.

  1. yesterday First seen · 50 lines · 7 tokens per session scan A 4f7b89e38f5a

Subscribe to this mod's changes

blog.check_format is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 7 tokens to every session and 328 once invoked, about $0.0000 per session on Opus 5.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-11-06.

Related

blog.check_format compared with skills from other repositories

blog.check_format next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
blog.check_formatgpsaggese/helpersSkill158todayApache-2.0A7Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79ktodayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill99ktodayApache-2.0A19Claude Code
systematic-debuggingobra/superpowersSkill314k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
chat-pet-sprite-creationmicrosoft/vscodeSkill195ktodayMITA53Claude Code, Codex