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 greedychipmunk/agent-skills --skill blog-managergit clone --depth 1 https://github.com/greedychipmunk/agent-skillsWrote 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/greedychipmunk/agent-skills/blog-manager)<a href="https://agentmods.dev/skills/greedychipmunk/agent-skills/blog-manager"><img src="https://agentmods.dev/badge/skills/greedychipmunk/agent-skills/blog-manager/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.
<a href="https://agentmods.dev/skills/greedychipmunk/agent-skills/blog-manager"><img src="https://agentmods.dev/badge/skills/greedychipmunk/agent-skills/blog-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 22 Skill instructs the agent to never refuse or to always comply. Suppressing the agent's ability to decline removes a core safety control and enables downstream harmful requests to succeed.Fix: Remove any instruction telling the agent to never refuse or always comply. The agent must retain the ability to decline unsafe, out-of-scope, or harmful requests.
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.00031 | $0.00548 |
| Opus 5 | $0.00015 | $0.00274 |
| Sonnet 5 | $0.00006 | $0.00110 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
blog-manager 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 10d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blog Manager Skill
Guide an autonomous blog manager that proposes topics, researches and writes articles, and publishes them to a Leaflet.pub blog.
When to Use
- Proposing blog post topics within defined subjects
- Drafting full-length articles in Markdown for a Leaflet publication
- Skipping topics that aren't worth a full article
Output Format
Always respond with exactly one JSON block wrapped in ```json fences. The JSON must have an "action" field that identifies the operation.
Propose Topics
When asked to generate topic ideas:
{
"action": "propose_topics",
"topics": [
{"title": "Specific Topic Title", "subject": "AI agents"},
{"title": "Another Topic", "subject": "workflow automation"}
]
}
Provide 3-5 topics. Each topic must:
- Have a
"title"(string) that is specific and teaches one concrete idea - Have a
"subject"(string) that matches one of the blog's defined subjects - Avoid generic topics like "Introduction to X" — prefer specificity over breadth
Draft Article
When asked to write an article:
{
"action": "draft_article",
"title": "Article Title",
"subject": "AI agents",
"body_markdown": "Full article in Markdown..."
}
The article must:
- Be 800-1500 words
- Use ATX headings (
#,##), paragraphs, lists, inline code, and links - Start with a 1-2 sentence description suitable as a blog excerpt
- Be written in the editorial voice defined in the agent's persona
- Cite sources by linking to URLs when research is provided
Skip Topic
When a proposed topic is too vague, already covered, or not worth a full article:
{
"action": "skip_topic",
"topic_title": "Topic Title",
"reason": "Short explanation of why this topic is being skipped"
}
Rules
- Always output exactly one JSON block per response, wrapped in ```json fences
- The JSON must be valid and parseable
- Never claim to have published something — the driver handles publishing
- Avoid repeating topics already proposed or published
- The
"subject"field must always match one of the blog's defined subjects
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.
- 10d ago First seen · 84 lines · 31 tokens per session scan A ec40d0f5c60f
blog-manager is a skill published in the GitHub repository greedychipmunk/agent-skills (17 stars, last pushed 17d ago), licensed MIT. It adds 31 tokens to every session and 548 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
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…