sonicjs: Command for Claude Code

.claude/commands/sonicjs-seo-blog.md

sonicjs-seo-blog is a command for Claude Code from SonicJs-Org/sonicjs. It costs 0 tokens per session (1,108 once invoked), scanned A, original, MIT.

A command that researches a topic and generates a 1,500–2,500-word search-optimized blog post for SonicJS, using the supplied topic.

In plain words
What is it for?
Use it to create a SonicJS article with a title, summary box, primary and secondary keywords, competitor-informed content, and documentation links.
Why use it?
It organizes keyword research, search intent, headings, code examples, links, and a call to action into one draft.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths.

This is SonicJs-Org/sonicjs's own configuration. It tells Claude Code how to work on sonicjs itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything sonicjs configures →

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/lane/Dropbox/Data/.env.

About the project

SonicJS is a TypeScript-first headless content-management system that exposes content through REST APIs and an administrative interface, running on Cloudflare Workers or other SQLite-compatible environments. It is for developers building applications that manage and publish structured content, with storage through technologies such as D1 and R2. Catalogue add-ons help coding agents create and work with SonicJS projects and content.

SonicJs-Org/sonicjs · 1,700 stars · on GitHub · sonicjs.com

Reuse

Borrowing it

Nothing to install: this file belongs to SonicJs-Org/sonicjs. 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/SonicJs-Org/sonicjs/main/.claude/commands/sonicjs-seo-blog.md
Clone the repo
git clone --depth 1 https://github.com/SonicJs-Org/sonicjs

Made for: Claude Code.

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 sonicjs-seo-blog

README.md
[![agentmods](https://agentmods.dev/badge/commands/sonicjs-org/sonicjs/sonicjs-seo-blog/github.svg)](https://agentmods.dev/commands/sonicjs-org/sonicjs/sonicjs-seo-blog)
Your own site
<a href="https://agentmods.dev/commands/sonicjs-org/sonicjs/sonicjs-seo-blog"><img src="https://agentmods.dev/badge/commands/sonicjs-org/sonicjs/sonicjs-seo-blog/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.

agentmods 80×15 button for sonicjs-seo-blog

Your own site · 80×15
<a href="https://agentmods.dev/commands/sonicjs-org/sonicjs/sonicjs-seo-blog"><img src="https://agentmods.dev/badge/commands/sonicjs-org/sonicjs/sonicjs-seo-blog.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 1,108 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01108
Opus 5 $0.00000 $0.00554
Sonnet 5 $0.00000 $0.00222
Haiku 4.5 $0.00000 $0.00111

Measured 10d ago against content hash a285cea272d0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

sonicjs-seo-blog scanned grade A with 1 finding 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 10d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

4. Call `POST https://api.openai.com/v1/images/generations` with `model: dall-e-3`, `size: 1792x1024`, `quality: hd`, `style: vivid`, `n: 1`. Use a `Bash` curl call so the key never enters the prompt.
.claude/commands/sonicjs-seo-blog.md · 87 lines

How it starts

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

Generate SEO-Optimized Blog Post

Generate a high-quality, SEO-optimized blog post for SonicJS on the topic: $ARGUMENTS

Instructions

  1. Research Phase:

    • Search the web for current trends and competitor content on this topic
    • Identify the primary keyword and 3-5 secondary keywords
    • Find the search intent (informational, transactional, navigational)
  2. Content Creation:

    • Write a comprehensive blog post (1500-2500 words)
    • Use proper heading hierarchy (H1 > H2 > H3)
    • IMPORTANT: Include a TL;DR box with Key Stats immediately after the H1 (see format below)
    • Include code examples where relevant (use SonicJS syntax)
    • Add internal links to SonicJS documentation
    • Include a clear call-to-action
  3. TL;DR Box (Required for Featured Snippets): Place this immediately after the H1 title:

    > **TL;DR** — [2-3 sentence summary directly answering the main question]
    >
    > **Key Stats:**
    > - [Specific number/metric - e.g., "Under 50ms response time globally"]
    > - [Specific number/metric - e.g., "Zero cold starts with V8 isolates"]
    > - [Specific number/metric - e.g., "300+ edge locations worldwide"]
    

    Why this matters:

    • Featured snippets can increase CTR by 8.6%
    • AI Overviews (Google SGE) extract from concise summaries
    • Voice search prefers 2-3 sentence answers
    • 35% increase in AI visibility reported with TL;DR sections
  4. SEO Elements:

    • Meta title (50-60 characters)
    • Meta description (150-160 characters)
    • URL slug (lowercase, hyphenated)
    • OpenGraph tags
    • Target keyword density: 1-2%
  5. Output Format: Create the blog post as an MDX file with frontmatter metadata.

  6. Hero Image Generation (REQUIRED — always run): After writing the MDX file, you MUST generate a hero image for the post. Do not skip this step and do not ask the user — image generation is part of every blog post.

    Procedure:

    1. Create the directory www/public/images/blog/[generated-slug]/ if it doesn't exist.
    2. Source the env file: source /Users/lane/Dropbox/Data/.env to load OPENAI_API_KEY.
    3. Build a DALL-E prompt using the brand guidelines and category template from the sonicjs-blog-image skill (.claude/commands/sonicjs-blog-image.md):
      • 3D isometric visualization, dark slate background nearly black, electric blue (#3B82F6) glowing accents, futuristic enterprise tech aesthetic, no text/letters/logos.
      • Pick the template that matches the post category (Tutorial, Comparison, Technical Deep Dive, or Use Case).
    4. Call POST https://api.openai.com/v1/images/generations with model: dall-e-3, size: 1792x1024, quality: hd, style: vivid, n: 1. Use a Bash curl call so the key never enters the prompt.
    5. Download the returned image URL (URLs expire in ~1 hour) to www/public/images/blog/[generated-slug]/hero.png using curl -o.
    6. Verify the file exists and is non-empty.
    7. Confirm the MDX frontmatter featuredImage.url points to /images/blog/[generated-slug]/hero.png and matches the saved file.

Read the full file on GitHub · 87 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. 10d ago First seen · 87 lines · 0 tokens per session scan A a285cea272d0

Subscribe to this mod's changes

sonicjs-seo-blog is a command published in the GitHub repository SonicJs-Org/sonicjs (1,700 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,108 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.