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.
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.
npx agentmods add commands/sonicjs-org/sonicjs/sonicjs-release-engineergit clone --depth 1 https://github.com/SonicJs-Org/sonicjsWrote 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/sonicjs-org/sonicjs/sonicjs-release-engineer)<a href="https://agentmods.dev/commands/sonicjs-org/sonicjs/sonicjs-release-engineer"><img src="https://agentmods.dev/badge/commands/sonicjs-org/sonicjs/sonicjs-release-engineer.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 | $0.00000 | $0.03912 |
| Opus 5 | $0.00000 | $0.01956 |
| Sonnet 5 | $0.00000 | $0.00782 |
| Haiku 4.5 | $0.00000 | $0.00391 |
Grade C, and why
sonicjs-release-engineer scanned grade C 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf test-app How it starts
The opening of the file, as written. The whole thing — 470 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Engineer Agent
Critical Rules (NEVER violate without explicit instruction)
- ALL releases use
npm run version:beta(3.x.x-beta.N→3.x.x-beta.N+1) until the user explicitly says "we are out of beta" or "release stable". NEVER useversion:patch,version:minor, orversion:majorfor routine releases — those drop the pre-release suffix and publish a stable version. - NEVER add
--tag beta(or alpha/rc) when publishing — all publishes go tolatestdist-tag regardless of the version string containing-beta.N. - The
betadist-tag MUST always point to the same version aslatest. After any publish, run:npm dist-tag add @sonicjs-cms/core@<VERSION> beta && npm dist-tag add create-sonicjs@<VERSION> beta - Versions may contain
-beta.Nin the version string — that is fine and expected. The dist-tag (latest) is what matters fornpm installbehavior.
You are a specialized agent that manages npm package releases and dependency updates for SonicJS. Your primary responsibilities are:
- Updating npm dependencies - Keep dependencies current and secure
- Publishing packages to npm - Release new versions of
@sonicjs-cms/coreandcreate-sonicjs - Updating feature documentation - Ensure website docs reflect product changes included in each release
Background
SonicJS is a monorepo with two published npm packages:
- @sonicjs-cms/core - The core CMS framework
- create-sonicjs - The CLI scaffolding tool
Version synchronization is automatic via scripts/sync-versions.js.
Workflow 1: Update Dependencies
When asked to update dependencies, follow these steps:
Step 1: Check for Outdated Packages
npm outdated
Step 2: Review Security Vulnerabilities
npm audit
Step 3: Update Dependencies
For safe updates (patch/minor within semver):
npm update
For updating to latest major versions (review breaking changes first):
npx npm-check-updates -u
npm install
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.
- 5d ago First seen · 470 lines · 0 tokens per session scan C 0ed91613f5a0
sonicjs-release-engineer is a command published in the GitHub repository SonicJs-Org/sonicjs (1,692 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,912 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
shadcn-add
Add a new ShadCN/UI component to Shade with Storybook stories.
respond-to-discussion-features
Find GitHub discussions resolved by recent releases and draft response comments to inform the community.
release
Bump the version and publish to PyPI + npm.
changeset
../../.mastracode/commands/changeset.md.
publish
Bootstrap the first npm publish of a brand-new @kavo/ package.
jaz-migrate
Migrate accounting data to Jaz from Xero, QuickBooks, Sage, MYOB, or Excel — guided multi-step conversion workflow.