Agent Skills is a collection and marketplace of reusable instruction sets that teach AI agents specific workflows, tasks, or domain knowledge, with supporting files such as scripts, templates, and examples. It is for people who want to install, browse, create, or contribute portable skills for compatible agents. The catalogue entries are individual skills from this collection.
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 block/agent-skills --skill goose-blog-postgit clone --depth 1 https://github.com/block/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/block/agent-skills/goose-blog-post)<a href="https://agentmods.dev/skills/block/agent-skills/goose-blog-post"><img src="https://agentmods.dev/badge/skills/block/agent-skills/goose-blog-post/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/block/agent-skills/goose-blog-post"><img src="https://agentmods.dev/badge/skills/block/agent-skills/goose-blog-post.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00018 | $0.03279 |
| Opus 5 | $0.00009 | $0.01639 |
| Sonnet 5 | $0.00004 | $0.00656 |
| Haiku 4.5 | $0.00002 | $0.00328 |
Grade A, and why
goose-blog-post 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 9d 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 — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goose Blog Post
Write blog posts for the block/goose open source project blog powered by Docusaurus.
Prerequisites
- The goose repo must be cloned locally
- Locate the blog directory at
<goose-repo>/documentation/blog/ - Confirm the
authors.ymland blog directory exist before proceeding
If the repo is not cloned, clone it:
gh repo clone block/goose
Workflow
Step 1: Determine the Writing Mode
Ask the user how they want to work. There are three modes:
-
"I have a draft" — The author has written (or will write) their own content. The agent scaffolds the directory, frontmatter, and image setup, then places the author's content into the correct format and reviews it against blog conventions.
-
"I have notes/an outline" — The author has rough ideas, bullet points, or an outline. The agent expands these into a full draft while preserving the author's voice and key points. Present the draft for the author's review before finalizing.
-
"Write it for me" — The author provides a topic and key points. The agent writes the full post. Present the draft for the author's review before finalizing.
Important: For modes 1 and 2, the author's voice and intent take priority. Do not rewrite their content unnecessarily. Focus on structure, conventions, and polish — not on replacing their words.
Step 2: Gather the Blog Post Details
Ask the user for the following (do not assume any of these):
- Topic: What is the blog post about?
- Author: Who is the author? (needs to match a key in
authors.yml) - Target audience: Who is this for? (developers, beginners, community, etc.)
For modes 2 and 3, also ask: 4. Key points: What are the main things the post should cover? 5. Tone: Technical deep-dive, casual walkthrough, announcement, etc.?
For mode 1, ask: 4. Where is the draft? A file path, or ask them to paste it in.
Step 3: Verify Author Exists
Check <goose-repo>/documentation/blog/authors.yml for the author key.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 335 lines · 18 tokens per session scan A 22ecdf59ab79
goose-blog-post is a skill published in the GitHub repository block/agent-skills (24 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 3,279 once invoked, about $0.0001 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
content-draft
Blog/newsletter/content writing skill.
aws-documentation-mcp
Tools to access AWS documentation, search for content, and get recommendations.
Blog Outline Generator
Generates a detailed, SEO-optimized blog post outline with H2/H3 structure, key points per section, and a hook.
FAQ Generator
Generates a comprehensive FAQ section for any product, API, or documentation page.
Technical Blog Post Writer
Writes engaging, accurate technical blog posts targeted at developer audiences.
image-generation
Generate or edit images via Codex CLI — with prompt refinement, vision validation, retry loop, and error handling.