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/let-sunny/canicode/developgit clone --depth 1 https://github.com/let-sunny/canicodeWhat 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.00488 |
| Opus 5 | $0.00000 | $0.00244 |
| Sonnet 5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
develop 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.
What it actually says
Run the automated development pipeline for a GitHub issue.
Input: $ARGUMENTS (issue number, or --resume <run-dir> with optional --from <step>)
Instructions
Run the development script:
npx tsx scripts/develop.ts $ARGUMENTS
The script (scripts/develop.ts) orchestrates:
- Plan (Agent) — Read issue, explore codebase, produce plan.json
- Implement (Agent) — Write code per plan, commit, produce implement-log.json
- Test (CLI, non-blocking) —
pnpm lint && pnpm test:run, failures forwarded to Review - Review (Agent) — Independent review with intent-conflict awareness
- Fix (Agent) — Fix review findings while preserving implementation intent
- Verify (CLI + circuit breaker) —
pnpm lint && pnpm test:run && pnpm build, auto-retry with re-plan - PR (CLI) —
gh pr create --draft
State tracked in logs/develop/<issue>--<timestamp>/index.json.
After the script completes
Report the summary from index.json:
- Which steps completed, skipped, or failed
- Plan summary and task count
- Review verdict and finding counts
- Circuit breaker state (if verify needed retries)
- PR URL (if created)
- Path to the run directory
Examples
# New run
npx tsx scripts/develop.ts 236
# Resume from failure
npx tsx scripts/develop.ts --resume logs/develop/236--2026-04-16-1200
# Resume from specific step (name or 1-based index: plan=1, implement=2, test=3, review=4, fix=5, verify=6, pr=7)
npx tsx scripts/develop.ts --resume logs/develop/236--2026-04-16-1200 --from review
Rules
- The script handles all orchestration — do NOT manually run individual steps.
- If the script fails, check
$RUN_DIR/index.jsonfor the failed step and error. - To re-run from a specific step, use
--resumewith--from.
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 · 52 lines · 0 tokens per session scan A 4b3396c803fa
develop is a command published in the GitHub repository let-sunny/canicode (10 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 488 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-31.
Other commands, from other repositories
release
Command "release" from GLips/Figma-Context-MCP, covering release and steps.
open
SoDam-Design-Kit open 대시보드 — 검증 이력·판정서·스크린샷을 브라우저로 열람 + 재검증.
setup
SoDam-Design-Kit 설정 마법사 — config.json 생성 + shadcn 컴포넌트 스캔으로 component-map 초기 시드.
ds-add
Kullanıcı bir Figma linki ile yeni tasarım sistemi eklemek istediğinde bu komutu kullan. Bu komut yeni ekleme ve güncelleme arasındaki farkı otomatik tespit eder.
ds-sync
Mevcut bir tasarım sistemi kütüphanesini Figma'dan senkronize eder. Tam sync, kısmi sync ve resume (yarım kalanı devam ettirme) destekler.
ds-validate
Kullanıcı "kütüphane doğrula", "DS'i validate et", "cache'i kontrol et", "DS uyumunu denetle" dediğinde bu komutu uygula. Eklenmiş DS'lerin repo template + user-local cache + state dosyalarının birbiriyle tutarlı olduğunu denetler.