Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/commands/pmdevsolutions/aurelius/create-blog-article)<a href="https://agentmods.dev/commands/pmdevsolutions/aurelius/create-blog-article"><img src="https://agentmods.dev/badge/commands/pmdevsolutions/aurelius/create-blog-article.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.00017 | $0.03912 |
| Opus 5 | $0.00009 | $0.01956 |
| Sonnet 5 | $0.00003 | $0.00782 |
| Haiku 4.5 | $0.00002 | $0.00391 |
Grade A, and why
create-blog-article 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 yesterday.
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
100% identical to create-blog-article — 1 line 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 — 431 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Blog Article for Claude Code Component
You will create a complete, SEO-optimized blog article for a Claude Code component.
Component Path Argument
Component path provided: $ARGUMENTS
Expected format examples:
development-team/frontend-developer(for agents)supabase(for MCPs)productivity/nowait(for skills)
Step 1: Identify Component Type and Read Component File
Based on the path structure, determine the component type:
- If path has
/, could be an agent, MCP, command, skill, or hook in a folder - Single word could be MCP, command, or skill
Read the component file:
- Agents:
cli-tool/components/agents/$ARGUMENTS.md(e.g.,development-team/frontend-developer.md) - MCPs:
cli-tool/components/mcps/$ARGUMENTS.json(e.g.,devtools/context7.json) - Skills:
cli-tool/components/skills/$ARGUMENTS/SKILL.md - Commands:
cli-tool/components/commands/$ARGUMENTS.md(e.g.,setup/ci-cd-pipeline.md) - Hooks:
cli-tool/components/hooks/$ARGUMENTS.md
CRITICAL: Use find or grep to locate the actual file path first, then extract folder/name structure.
Extract from the component file:
name: Component namedescription: Component descriptiontools: Available tools (for agents)- Key capabilities and focus areas from the content
Step 2: Generate Component-Specific Blog ID and Names
From the component path, create:
-
Blog ID: Convert path to blog-friendly ID
- Example:
development-team/frontend-developer→frontend-developer-agent - Example:
supabase→supabase-mcp - Example:
productivity/nowait→nowait-skill
- Example:
-
Component Name: Human-readable name
- Example:
frontend-developer→Frontend Developer - Example:
supabase→Supabase
- Example:
-
Component Type: Uppercase type
- AGENT, MCP, SKILL, COMMAND, HOOK
Step 3: Generate Cover Image FIRST
CRITICAL: Generate the cover image BEFORE creating the HTML file.
Use the Python script to generate the image:
python3 scripts/generate_blog_images.py
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.
- yesterday First seen · 431 lines · 17 tokens per session scan A 3053e7466512
create-blog-article is a command published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 21d ago), licensed MIT. It adds 17 tokens to every session and 3,912 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to create-blog-article, differing in 1 line, and is treated as a copy.
Other commands, from other repositories
figma-start
디자이너가 개발자의 원본 PR 위에서 검수를 시작할 때 호출하는 커맨드입니다. PR 링크 하나만 주면 프로젝트 클론부터 합니다 — 검수할 프로젝트를 미리 받아둘 필요가 없습니다. 브랜치 생성·체크아웃 후 빌드해서 기기에 올려 화면까지 띄워줍니다 — 실행할 기기·에뮬레이터가 없으면 검수에 맞는 걸 설치해서 만듭니다. 그 브랜치의 커밋 이력 패널도 개발툴에 띄워줍니다 — 지금까지 반영한 검수 내용을 검수 내내 옆에 두고 볼 수 있습니다. 커밋·푸시는 하지 않습니다. 디자이너가 화면을 먼저 확인한 뒤, 필요하면 /figma-apply로 피그마 변경을 반영합니다.
handoff
디자이너 작업 완료 신호 — design/ 브랜치로 dev 브랜치 타겟 PR을 만들고, 원본 dev PR 작성자를 리뷰어로 지정.
figma-apply
피그마 변경을 현재 design/ 브랜치에 반영(커밋·푸시). /figma-start 이후에 사용.
test
Run tests and ensure code quality for the Figma Console MCP server.
design-tutorial
Interactive guided tour of Naksha — learn commands through real exercises, discover workflows, and get oriented in under 10 minutes.
figma-component-library
Generate a complete component library in Figma from a design system config — atoms, molecules, and organisms with all variants, auto layout, and component properties.