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/hamr0/liteagents/releasegit clone --depth 1 https://github.com/hamr0/liteagentsWhat 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.00021 | $0.01285 |
| Opus 5 | $0.00010 | $0.00642 |
| Sonnet 5 | $0.00004 | $0.00257 |
| Haiku 4.5 | $0.00002 | $0.00128 |
Grade A, and why
release 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
End-to-end feature-delivery orchestrator. It does not re-implement
checks — it runs your existing gates (/ship, /security, /diff-review)
under /verify-done discipline, then performs the release actions. Two halves
split by a hard gate: everything before the gate is safe and read-only;
everything after rewrites history and is confirmed step by step.
A feature branch is required — main is only the merge target. $ARGUMENTS
names the branch to release. Omit it only if you are already on a feature
branch. If you are on main with nothing named, a branch is created for you —
but you should be releasing a deliberately-named feature branch.
Phase 0 — Preflight (resolve a feature branch — never main)
- Resolve the release branch — whatever gets merged into
main:$ARGUMENTSgiven →git switchto it (create it if it does not exist).- else not on
main→ release the current branch. - else on
mainwith no arg → createfeat/<slug>(named for the change) and carry your working changes onto it. Never releasemain.
- Land the feature on the branch — if the working tree still has uncommitted feature changes, commit them now; the gates must review a real diff, not a dirty tree.
git fetch origin; the release diff isorigin/main...HEAD(now guaranteed to be the resolved branch). If it is empty, stop — nothing to release.- Print a one-line plan: branch · commit count · files changed.
Phase 1 — VERIFY (delegate; no hand-waving)
First, load the real checklists. Locate and read the sibling command
definitions so you apply their exact checks, not an approximation — glob your
installed commands/skills for ship.md, security.md, diff-review.md, and
verify-done (a skill or command). If one cannot be found, run that check from
its name and flag that its full checklist was unavailable — never pretend
it passed.
Then run each gate and capture fresh evidence — the exact command, its exit
code, and the result. Per /verify-done: a check you did not actually run
is a FAIL, never an assumed pass.
/ship— pre-deploy gate (tests, lint, build, secrets, authz, rate limit, data scope, migrations, docs-sync)./security— on the changed files./diff-review— onorigin/main...HEAD.
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 · 91 lines · 21 tokens per session scan A 58070ae37e54
release is a command published in the GitHub repository hamr0/liteagents (22 stars, last pushed 3d ago), licensed Apache-2.0. It adds 21 tokens to every session and 1,285 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-30.
Other commands, from other repositories
profile
Save, apply, and share multi-agent configuration profiles.
rollback
Restore a skill to its previous version. Requires a history entry — created automatically when you use rolecraft update or re-install over an existing skill.
rclone_convmv
Convert file and directory names in place.
init
Generate FILETREE.md from scratch. Confirms overwrite if it already exists. --self-only keeps every artifact out of git.
rclone_copy
Copy files from source to dest, skipping identical files.
uninstall
Uninstall filetree from this repo — un-wires CLAUDE.md/AGENTS.md, removes generated artifacts (confirmed per item), tears down self-only mode if enabled.