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 instructions/sonicjs-org/sonicjs/claude-mdgit 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/instructions/sonicjs-org/sonicjs/claude-md)<a href="https://agentmods.dev/instructions/sonicjs-org/sonicjs/claude-md"><img src="https://agentmods.dev/badge/instructions/sonicjs-org/sonicjs/claude-md.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.04697 | $0.04697 |
| Opus 5 | $0.02348 | $0.02348 |
| Sonnet 5 | $0.00939 | $0.00939 |
| Haiku 4.5 | $0.00470 | $0.00470 |
Grade C, and why
sonicjs CLAUDE.md 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 4d 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 node_modules package-lock.json && npm install How it starts
The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SonicJS AI Development Guidelines
Cloudflare-native headless CMS built with Hono.js + TypeScript on Cloudflare Workers / D1.
Core Technology Stack
- Framework: Hono.js
- Runtime: Cloudflare Workers
- Database: Cloudflare D1 (SQLite) with Drizzle ORM (legacy only — document layer is raw SQL)
- Validation: Zod
- Testing: Vitest (unit + real-SQLite) + Playwright (E2E)
- Frontend: HTMX + HTML tagged templates (admin UI)
- Auth: Better Auth (session + RBAC) —
c.get('user') === { userId, email, role } - Deployment: Wrangler
Workspace boundary (Conductor)
- Work in
.conductor/hong-kong-v3/. Never read or write/Users/lane/Dev/refs/sonicjs/(sibling main checkout). - Target branch:
origin/v3. PRs:gh pr create --base v3. Diff:git diff origin/v3....
Architecture direction: Document Model (authoritative)
The project is migrating from per-feature tables (content, media, testimonials, email_log, …) to a unified document repository. All new features build on the document model. Do not add new feature tables.
Full design + remediation runbook: docs/ai/plans/document-model-poc-plan.md (Appendix A = original design; §1–§7 = current implementation status, defect IDs D1–D48).
The 5 document tables (migration 0002_documents.sql)
document_types— registered schemas (code/plugin-owned).documents— every content/media/plugin record + every historical version. Queryable scalar fields are exposed as indexed JSONVIRTUALgenerated columns (q_*) on this table —json_extract(data, '$.path').document_references— typed strong/weak edges (FK todocuments); powers "where used" and reference-aware delete.document_facets— indexed rows for multi-valued scalar fields (e.g.tags) — the one case generated columns can't cover.document_permissions— per-document ACL overrides on top of type-level base grants.
Implementation rules (non-negotiable — each line is a bug already shipped)
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.
- 4d ago First seen · 304 lines · 4,697 tokens per session scan C 2e1b5f64751f
sonicjs CLAUDE.md is an instructions file published in the GitHub repository SonicJs-Org/sonicjs (1,692 stars, last pushed yesterday), licensed MIT. It adds 4,697 tokens to every session, about $0.0235 per session on Opus 5. 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 instructions, from other repositories
agentos CLAUDE.md
Claude Code instructions for rivet-dev/agentos, covering agentos, boundaries, security model, sqlite schema ownership and runtime and registry.
prest copilot-instructions.md
Copilot instructions for prest/prest, covering copilot instructions for prest go backend, project scope, core engineering principles, solid principles for go and s — single responsibility.
intlayer CLAUDE.md
Claude Code instructions for aymericzip/intlayer, covering repo layout, commands (run from root), content declaration flow, git and commit conventions.
gorest AGENTS.md
AGENTS.md instructions for pilinux/gorest, covering agents.md, project overview, build and run commands, build and tidy dependencies.
invoice-builder copilot-instructions.md
Copilot instructions for piratuks/invoice-builder, a project described as: Invoice and quotation builder desktop app with PDF export, designed for small businesses and freelancers. Create, manage, and export invoices and quotes easily using a local database in an Electron-based app.
data-api-builder copilot-instructions.md
Copilot instructions for Azure/data-api-builder, covering data api builder (dab) - copilot instructions, project overview, key technologies, project structure and building and testing.