What is sonicjs-seo-keywords?

A command for researching search terms related to SonicJS, a TypeScript content-management system for building and serving website content. It examines competitors, search intent, and groups of related keywords.

Use it to research product, platform, feature, long-tail, and problem-solving keywords, including terms related to headless CMSs, Cloudflare, serverless systems, and SonicJS alternatives.

It helps identify what people search for and where a SonicJS website may have opportunities to appear in search results.

How SonicJs-Org/sonicjs configures Claude Code

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,697 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-keywords.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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/sonicjs-org/sonicjs/sonicjs-seo-keywords/github.svg)](https://agentmods.dev/commands/sonicjs-org/sonicjs/sonicjs-seo-keywords)

Your own site

<a href="https://agentmods.dev/commands/sonicjs-org/sonicjs/sonicjs-seo-keywords"><img src="https://agentmods.dev/badge/commands/sonicjs-org/sonicjs/sonicjs-seo-keywords/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/sonicjs-org/sonicjs/sonicjs-seo-keywords"><img src="https://agentmods.dev/badge/commands/sonicjs-org/sonicjs/sonicjs-seo-keywords.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 619 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.00619
Opus 5	$0.00000	$0.00309
Sonnet 5	$0.00000	$0.00124
Haiku 4.5	$0.00000	$0.00062

Measured 9d ago against content hash 1b83493b7a2f, 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-keywords 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 9d 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.

.claude/commands/sonicjs-seo-keywords.md · 96 lines

How it starts

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

Keyword Research for SonicJS

Perform keyword research to identify ranking opportunities for SonicJS.

Research Process

1. Competitor Analysis

Search the web to analyze what keywords competitors rank for:

Strapi - Most popular open-source headless CMS
Sanity - Developer-focused CMS
Contentful - Enterprise headless CMS
Payload CMS - TypeScript headless CMS
Directus - Open-source data platform
KeystoneJS - Node.js headless CMS

2. Keyword Categories

Core Product Keywords

headless cms
open source cms
typescript cms
api-first cms

Platform-Specific Keywords

cloudflare workers cms
cloudflare d1 cms
edge cms
serverless cms
hono framework cms

Feature Keywords

cms with rest api
cms with admin panel
self-hosted headless cms
developer-friendly cms

Long-tail Keywords

how to build headless cms
best cms for cloudflare
typescript content management
jamstack cms comparison

Problem-Solution Keywords

wordpress alternative for developers
strapi alternative
contentful free alternative
cms without database server

3. Search Intent Analysis

For each keyword, identify:

Informational: Learning/researching (target with blog posts)
Navigational: Looking for specific site (ensure brand presence)
Transactional: Ready to use/buy (target with landing pages)
Commercial: Comparing options (target with comparison content)

Output Format

Create a keyword research report with:

## Keyword Research Report - SonicJS

### High Priority Keywords (Monthly Search Volume)

| Keyword | Volume | Difficulty | Intent | Current Rank | Target Content |
|---------|--------|------------|--------|--------------|----------------|
| headless cms | 10K+ | High | Commercial | N/A | Comparison page |
| typescript cms | 1K | Medium | Commercial | N/A | Homepage |
| cloudflare cms | 500 | Low | Informational | N/A | Tutorial |

### Quick Win Opportunities
[Keywords with low difficulty where SonicJS could rank quickly]

### Content Gaps
[Topics competitors cover that SonicJS doesn't]

### Recommended Content Calendar
[Prioritized list of content to create]

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

9d ago First seen · 96 lines · 0 tokens per session scan A 1b83493b7a2f

Subscribe to this mod's changes

sonicjs-seo-keywords is a command published in the GitHub repository SonicJs-Org/sonicjs (1,697 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 619 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-08-30.

Marketing and SEO api cloudflare-workers cms headless-cms javascript rest-api

sonicjs: Command for Claude Code