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/atuljha23/holocron/developgit clone --depth 1 https://github.com/atuljha23/holocronWhat 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.00027 | $0.00365 |
| Opus 5 | $0.00014 | $0.00182 |
| Sonnet 5 | $0.00005 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
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 yesterday.
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
/holocron:develop
Feature: $ARGUMENTS
Run this in four explicit phases. Do not skip ahead.
Phase 1 — Research (delegate)
Spawn @architect (or @frontend-engineer / @backend-engineer depending on the feature) via the Agent tool to:
- Read adjacent code and summarize conventions.
- Identify reusable primitives already in the repo.
- List relevant constraints (data contracts, consumers, SLAs).
Cap the research report at ~300 words. Bring back file paths, not just prose.
Phase 2 — Plan (you)
With research in hand, enter plan mode (/holocron:plan-style scaffold). Present options if they exist. Get approval before writing code.
Phase 3 — Implement (you)
- Match conventions found in Phase 1.
- Minimum viable change. No speculative abstractions.
- Write a test first where the contract is clear; write the code, then the test when exploratory.
- Commit in atomic chunks — one logical change per commit.
Phase 4 — Review (delegate)
Spawn @code-reviewer on the diff. Surface blockers before handing back to the user. If the change is UI, also spawn @a11y-auditor. If server-side and non-trivial, @security-reviewer.
Exit
End with: summary of what was built, files changed, tests added, and the commands the user can run to verify.
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.
- yesterday First seen · 41 lines · 27 tokens per session scan A ccddbe5bd7f1
develop is a command published in the GitHub repository atuljha23/holocron (2 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 365 once invoked, about $0.0001 per session on Opus 5. 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
autopilot
Autonomous session-orchestration loop with kill-switches (Phase C-1.b — all 10 kill-switches shipped).
brainstorm
Run a lightweight Socratic design dialogue (3-5 AUQ rounds) and write a spec markdown file before any implementation work. Use BEFORE /plan feature when scope/UX is ambiguous.
contract-version-bump
Classify and apply a version bump to a machine-readable contract (JSON Schema, API spec, config schema) — version literals, consumer compatibility, changelog entry, downstream drift.
reconcile
Reconcile learnings into .claude/rules/ proposals — on-demand version of session-end Phase 3.6.8.
spinout
Guided 5-step venture-spinout / sanitized-fork runbook (copy + fresh-init + SNAPSHOT-FREEZE) — interactive, not scripted.
go
Approve session plan and begin wave execution.