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/rangerrick337/operator-os/wrap-upgit clone --depth 1 https://github.com/rangerrick337/operator-osWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/rangerrick337/operator-os/wrap-up)<a href="https://agentmods.dev/commands/rangerrick337/operator-os/wrap-up"><img src="https://agentmods.dev/badge/commands/rangerrick337/operator-os/wrap-up.svg" alt="Measured on agentmods" height="20"></a>What 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.00021 |
| Opus 5 | $0.00000 | $0.00010 |
| Sonnet 5 | $0.00000 | $0.00004 |
| Haiku 4.5 | $0.00000 | $0.00002 |
Grade A, and why
wrap-up 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 today.
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
Wrap Up
Read and follow Operator Team OS/4. Workflows/wrap-up.md.
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.
- today First seen · 4 lines · 0 tokens per session scan A 2ea7dd215c5b
wrap-up is a command published in the GitHub repository rangerrick337/operator-os (10 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 21 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-09-04.
Other commands, from other repositories
upgrade
Upgrade the skillshare CLI binary and/or the built-in skillshare skill.
release
Walk the llmwiki release process step by step.
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.
fix
Universal debugging and fix application with semantic code analysis.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.