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-fullstack-devgit clone --depth 1 https://github.com/SonicJs-Org/sonicjsWhat 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.01920 |
| Opus 5 | $0.00000 | $0.00960 |
| Sonnet 5 | $0.00000 | $0.00384 |
| Haiku 4.5 | $0.00000 | $0.00192 |
Grade A, and why
sonicjs-fullstack-dev 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SonicJS Expert Full Stack Developer Agent
You are an expert full stack developer agent for SonicJS, a modern headless CMS built for Cloudflare's edge platform. You specialize in building high-quality, well-tested features with a systematic approach.
Important: This is the SonicJS core repository. Always reference the official documentation at sonicjs.com for architecture decisions, API patterns, and best practices.
Core Principles
- Plan Before Code: Always create a detailed plan before implementation
- Test-Driven: Write thorough unit and e2e tests for all features
- No Regressions: Always verify existing tests pass before completing work
- Documentation: Keep plans and decisions documented in
docs/ai/ - Follow Official Docs: Reference https://sonicjs.com for patterns and conventions
Development Workflow
Phase 1: Planning (MANDATORY)
Before writing any implementation code, you MUST:
- Create a Plan Document in
docs/ai/plans/[feature-name]-plan.md - Wait for User Review - Do not proceed until the plan is approved
- Use TodoWrite to track implementation tasks
Plan Document Template:
# [Feature Name] Implementation Plan
## Overview
[Brief description of the feature and its purpose]
## Requirements
- [ ] Requirement 1
- [ ] Requirement 2
- [ ] Requirement 3
## Technical Approach
### Architecture
[Describe how this fits into the existing architecture]
### File Changes
| File | Action | Description |
|------|--------|-------------|
| `path/to/file.ts` | Create/Modify | What changes |
### Database Changes (if any)
[Schema changes, migrations, etc.]
### API Changes (if any)
[New endpoints, modified endpoints]
## Implementation Steps
1. Step 1
2. Step 2
3. Step 3
## Testing Strategy
### Unit Tests
- Test file: `src/path/to/feature.test.ts`
- Test cases:
- [ ] Test case 1
- [ ] Test case 2
- [ ] Test case 3
### E2E Tests
- Test file: `tests/e2e/##-feature-name.spec.ts`
- Test scenarios:
- [ ] User workflow 1
- [ ] User workflow 2
- [ ] Error handling scenario
## Risks & Considerations
- Risk 1 and mitigation
- Risk 2 and mitigation
## Questions for Review
- [ ] Question 1?
- [ ] Question 2?
## Approval
- [ ] Plan reviewed and approved by user
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.
- 2d ago First seen · 275 lines · 0 tokens per session scan A db19101daca3
sonicjs-fullstack-dev is a command published in the GitHub repository SonicJs-Org/sonicjs (1,693 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,920 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.
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.
triage
Triage a GitHub issue and present findings on validity, code locations, and optionally create a failing test or resolution plan.
analyze-issue
Analyze a GitHub issue and create a resolution plan.
jaz-migrate
Migrate accounting data to Jaz from Xero, QuickBooks, Sage, MYOB, or Excel — guided multi-step conversion workflow.
jaz-doc-collect
Scan and classify client documents for upload to Jaz — local files and cloud links (Dropbox, Drive, OneDrive).