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/causify-ai/helpers/blog.check_formatnpx skills add causify-ai/helpers --skill blog.check_formatgit clone --depth 1 https://github.com/causify-ai/helpersWrote 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/causify-ai/helpers/blog.check_format)<a href="https://agentmods.dev/skills/causify-ai/helpers/blog.check_format"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/blog.check_format.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.00007 | $0.00337 |
| Opus 5 | $0.00003 | $0.00169 |
| Sonnet 5 | $0.00001 | $0.00067 |
| Haiku 4.5 | $0.00001 | $0.00034 |
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 5d 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.
What it actually says
Goal
- Check that all the actual and the draft blogs have the correct format
Workflow
Step 1: Find Files
- Look for all the markdown files both
SKILL.mdand<TOPIC>.rules.md> find website/docs/blog/post -name "*.md"
Step 2: Read Context
- Read context about rules from
.claude/skills/blog.rules.md.claude/skills/markdown.rules.md.claude/skills/text.rules.md
Step 3: Check Rules
- For each file apply all the following rules and report violations as described below
Check Front Matter
- Make sure to follow the section
# Blog Document Structurefrom the file.claude/skills/blog.rules.md
Check that Has a TL;DR
- Make sure to follow the section
# Blog Document Structurefrom the file.claude/skills/blog.rules.md
Check for Other Violations
- Use the rules in
.claude/skills/blog.rules.mdto look for clear violations - Report them only if you are really sure about it
Step 4: Report Violations
- Report all the violations in a file
cfileusing the format in.claude/skills/cfile.rules.md
Step 5: Ask Users Whether to Fix the Problems
- Ask for the user which problems should be fixed by printing a list of problem with indices
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.
- 5d ago First seen · 48 lines · 7 tokens per session scan A 51bfcc8d1422
blog.check_format is a skill published in the GitHub repository causify-ai/helpers (145 stars, last pushed yesterday), licensed Apache-2.0. It adds 7 tokens to every session and 337 once invoked, about $0.0000 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…