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 eitelcj/Claude-Weekend --skill blog-draftgit clone --depth 1 https://github.com/eitelcj/Claude-WeekendWrote 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/eitelcj/claude-weekend/blog-draft)<a href="https://agentmods.dev/skills/eitelcj/claude-weekend/blog-draft"><img src="https://agentmods.dev/badge/skills/eitelcj/claude-weekend/blog-draft.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.1 | $0.00047 | $0.02071 |
| Opus 5 | $0.00023 | $0.01035 |
| Sonnet 5 | $0.00009 | $0.00414 |
| Haiku 4.5 | $0.00005 | $0.00207 |
Grade A, and why
blog-draft 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 7d 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.
This is a copy
91% identical to blog-draft — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding. User should provide:
- Idea/Topic: The main concept or theme for the blog post
- Resources: URLs, files, or references to research (optional but recommended)
- Target audience: Who the blog post is for (optional)
- Tone/Style: Formal, casual, technical, etc. (optional)
IMPORTANT: If the user is requesting updates to an existing blog post, skip steps 0-8 and start directly at Step 9. Read the existing draft file(s) first, then proceed with the iteration process.
Execution Flow
Follow these steps sequentially. Do not skip steps or proceed without user approval where indicated.
Step 0: Create Project Folder
-
Generate a folder name using format:
YYYY-MM-DD-short-topic-name- Use today's date
- Create a short, URL-friendly slug from the topic (lowercase, hyphens, max 5 words)
-
Create the folder structure:
blog-posts/ └── YYYY-MM-DD-short-topic-name/ └── resources/ -
Confirm folder creation with user before proceeding.
Step 1: Research & Resource Collection
-
Create
resources/subfolder in the blog post directory -
For each provided resource:
- URLs: Fetch and save key information to
resources/as markdown files - Files: Read and summarize in
resources/ - Topics: Use web search to gather up-to-date information
- URLs: Fetch and save key information to
-
For each resource, create a summary file in
resources/:resources/source-1-[short-name].mdresources/source-2-[short-name].md- etc.
-
Each summary should include:
# Source: [Title/URL] ## Key Points - Point 1 - Point 2 ## Relevant Quotes/Data - Quote or statistic 1 - Quote or statistic 2 ## How This Relates to Topic Brief explanation of relevance -
Present research summary to user.
Step 2: Brainstorm & Clarify
- Based on the idea and researched resources, present:
- Main themes identified from research
- Potential angles for the blog post
- Key points that should be covered
- Gaps in information that need clarification
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.
- 7d ago First seen · 275 lines · 47 tokens per session scan A 111cf3524535
blog-draft is a skill published in the GitHub repository eitelcj/Claude-Weekend (2 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 2,071 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to blog-draft, differing in 8 lines, and is treated as a copy.
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…
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…
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…