What is create-blog-post?

A command for drafting blog posts as MDX files, including posts made from scratch, from a template, or from existing documentation. MDX is a document format that allows Markdown and web components together.

It is for creating release announcements, tutorials, and other blog drafts for the Igniter.js website.

It avoids repeatedly setting up the required post location, metadata, and content structure for the website.

How felipebarcelospro/igniter-js configures GitHub Copilot

Reuse

Borrowing it

Nothing to install: this file belongs to felipebarcelospro/igniter-js. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/felipebarcelospro/igniter-js/main/.github/prompts/create-blog-post.md

Clone the repo

git clone --depth 1 https://github.com/felipebarcelospro/igniter-js

Made for: GitHub Copilot.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/felipebarcelospro/igniter-js/create-blog-post/github.svg)](https://agentmods.dev/commands/felipebarcelospro/igniter-js/create-blog-post)

Your own site

<a href="https://agentmods.dev/commands/felipebarcelospro/igniter-js/create-blog-post"><img src="https://agentmods.dev/badge/commands/felipebarcelospro/igniter-js/create-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/felipebarcelospro/igniter-js/create-blog-post"><img src="https://agentmods.dev/badge/commands/felipebarcelospro/igniter-js/create-blog-post.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 818 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00818
Opus 5.5	$0.00000	$0.00327
Sonnet 5.5	$0.00000	$0.00164
Haiku 4.5	$0.00000	$0.00082

Measured 1mo ago against content hash 9e72dea345c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-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 1mo 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.

.github/prompts/create-blog-post.md · 85 lines

How it starts

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

Prompt: Create Blog Post (Draft in MDX)

Purpose

Automate the creation of high-quality blog posts for the Igniter.js website. Support multiple creation modes: from scratch, from a template (e.g., release announcement), or by transforming existing documentation into a narrative article. Generate a complete MDX draft in the correct location with all required frontmatter and content sections.

Prerequisites

Website app located at apps/www.
Blog posts live under apps/www/src/app/(content)/blog/(posts)/<category>/<slug>/page.mdx.
Categories include (but are not limited to): announcements, tutorials.

Step-by-Step Instructions

Choose Creation Mode
- Ask the user to select one of the modes:
  1. From Scratch
  2. From Template (e.g., Release Announcement)
  3. From Documentation (transform doc into blog article)
Collect Metadata
- Title (H1 in the content; no frontmatter needed unless the site requires)
- Category (announcements | tutorials | custom)
- Slug (URL-friendly, kebab-case; if omitted, generate from title)
- Optional: short summary/abstract to include at the top.
Determine Output Path
- Path: apps/www/src/app/(content)/blog/(posts)/<category>/<slug>/page.mdx.
- Ensure the directory exists; create it if necessary.
Mode: From Scratch
- Ask for a brief outline or key points.
- Generate a complete article with:
  - H1 title
  - Intro paragraph setting context
  - Sections with H2/H3 headings
  - Code examples using fenced code blocks with appropriate language
  - Conclusion with next steps and links to docs
Mode: From Template (Release Announcement)
- Collect version (e.g., v0.12.0), date, and highlights.
- Fetch conventional commits since last tag if available to draft changes.
- Structure:
  - H1 Igniter.js <version> Released
  - Intro: what’s new and why it matters
  - Highlights (bulleted list)
  - Detailed changes grouped by type (Features, Fixes, Docs, Refactor, Perf, etc.)
  - Breaking Changes section (if any)
  - Upgrade guide: steps to update packages
  - Links to PRs/Issues

Read the full file on GitHub · 85 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.

1mo ago First seen · 85 lines · 0 tokens per session scan A 9e72dea345c3

Subscribe to this mod's changes

create-blog-post is a command published in the GitHub repository felipebarcelospro/igniter-js (240 stars, last pushed 29d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 818 tokens. 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-09-27.

Writing and docs api express fastify framework http middleware

create-blog-post next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
create-blog-postfelipebarcelospro/igniter-js	Command	240	29d ago	Apache-2.0	A	0	GitHub Copilot
focus-reporthoangsonww/Claude-Code-Agent-Monitor	Command	1.1k	yesterday	MIT	A	17	Claude Code
devgerard-labs/superpowers-api-platform	Command	2	5mo ago	MIT	A	35	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code

igniter-js: Command for GitHub Copilot