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/shipgit 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.00006 | $0.00567 |
| Opus 5 | $0.00003 | $0.00283 |
| Sonnet 5 | $0.00001 | $0.00113 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
ship 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
Pre-deploy / pre-merge gate. Detect the stack first (look for
package.json, pyproject.toml/setup.cfg, go.mod, Cargo.toml,
Makefile) and run only the checks that actually exist — never assume a
script (lint, build, migrate) is present. Report each item as
pass / fail / N/A.
Checklist
- Tests pass — run the project's real test command (
npm test,pytest,go test ./...,cargo test,make test). - Lint / format clean — only if a linter or formatter is configured.
- Build succeeds — only if the project has a build step.
- No debug leftovers — stray
console.log/print/debugger/dbg!/ commented-out blocks / blockerTODOs in the changed files. - No hardcoded secrets — scan the diff. Secrets load from env / a
secret store;
.envis gitignored and only a value-less.env.exampleis tracked. - Error handling complete — every new IO / network / DB call has a failure path; nothing fails silently; no internal detail leaks to clients.
- Authorization — new endpoints/actions check ownership + role, not just authentication (no IDOR via id-swapping).
- Rate limiting — new externally reachable routes, including authenticated writes, are bounded.
- Data access scoped & scales — new queries are constrained to the requesting principal (no cross-tenant leak) and avoid obvious N+1 / unindexed scans on hot paths.
- Migrations ready — only if the project has a schema / migrations.
- Docs & config in sync —
.env.example, README, and any threat-model / PRD updated for new config or new attack surface. - Clean tree, correct branch, in sync with
origin.
For any security-sensitive change in the diff, run /security on the
changed files before shipping.
Report: Ready 🚀 or Blocked 🛑 with the specific failing items.
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 · 41 lines · 6 tokens per session scan A 4c737e9c4576
ship is a command published in the GitHub repository hamr0/liteagents (22 stars, last pushed 3d ago), licensed Apache-2.0. It adds 6 tokens to every session and 567 once invoked, about $0.0000 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.