blog-post

blog-post is a skill for Claude Code, Codex from espennilsen/pi. It costs 48 tokens per session (572 once invoked), scanned A, original, MIT.

A writing and publishing workflow for blog posts on e9n.dev, a specific Eleventy-based website. Eleventy is a tool that turns text and templates into a static website, while Tailwind is a CSS toolkit used for styling.

In plain words
What is it for?
Use it to draft, revise, format, and publish posts with the site’s front matter, Tailwind classes, naming rules, and established author voice.
Why use it?
It keeps new and edited posts consistent with the site’s file format, layout, and direct technical writing style. It also covers the site-specific steps needed to publish them.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/espennilsen/pi/blog-post
Any agent
npx skills add espennilsen/pi --skill blog-post
Clone the repo
git clone --depth 1 https://github.com/espennilsen/pi

Made for: Claude Code, Codex.

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-post

README.md
[![agentmods](https://agentmods.dev/badge/skills/espennilsen/pi/blog-post.svg)](https://agentmods.dev/skills/espennilsen/pi/blog-post)
Your own site
<a href="https://agentmods.dev/skills/espennilsen/pi/blog-post"><img src="https://agentmods.dev/badge/skills/espennilsen/pi/blog-post.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 572 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00048 $0.00572
Opus 5 $0.00024 $0.00286
Sonnet 5 $0.00010 $0.00114
Haiku 4.5 $0.00005 $0.00057

Measured 5d ago against content hash 588fd0a1f076, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

skills/blog-post/SKILL.md · 72 lines

How it starts

The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Blog Post — e9n.dev

Write and publish blog posts for Espen's blog at /Users/espen/Dev/e9n.dev/.

Voice & Style

Espen's writing style:

  • Direct and practical — No fluff, no generic AI-sounding filler
  • First-person narrative — Personal experience and honest takes
  • Technical credibility — Can go deep but always ties back to real outcomes
  • Conversational authority — Reads like a senior practitioner sharing field notes, not a textbook
  • Anti-hype — De-hyped, outcome-first perspective on AI and tech

Avoid:

  • "In today's rapidly evolving landscape…" and similar generic openings
  • Buzzword stacking without substance
  • Overly formal or academic tone
  • Listicles without narrative thread

Process

  1. Read existing posts to match voice and format:

    ls /Users/espen/Dev/e9n.dev/src/posts/
    

    Read 2-3 recent posts to calibrate tone.

  2. Create the post file using the project's naming convention:

    /Users/espen/Dev/e9n.dev/src/posts/YYYY-MM-DD-slug.md
    
  3. Frontmatter template:

    ---
    title: "Post Title"
    description: "One-line description for SEO and social sharing"
    date: YYYY-MM-DD
    tags:
      - ai
      - sales
      - self-growth
    ---
    
  4. Structure:

    • Hook in the first paragraph (personal anecdote, bold claim, or question)
    • 2-4 main sections with practical takeaways
    • Concrete examples, code snippets, or frameworks where relevant
    • Close with a next action or reflection, not a generic summary
  5. Review checklist:

    • Does it sound like Espen, not an AI?
    • Is there a concrete takeaway in every section?
    • Would a senior technical/sales reader find this worth their time?
    • Is the frontmatter complete (title, description, date, tags)?

Preview

cd /Users/espen/Dev/e9n.dev && npm run dev

Common Tags

ai, sales, self-growth, agentic-ai, productivity, leadership, stoicism, infrastructure, devops, typescript

Read the full file on GitHub · 72 lines

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. 5d ago First seen · 72 lines · 48 tokens per session scan A 588fd0a1f076

Subscribe to this mod's changes

blog-post is a skill published in the GitHub repository espennilsen/pi (117 stars, last pushed 12d ago), licensed MIT. It adds 48 tokens to every session and 572 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens