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 skills add rangerrick337/operator-os --skill 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/skills/rangerrick337/operator-os/wrap-up)<a href="https://agentmods.dev/skills/rangerrick337/operator-os/wrap-up"><img src="https://agentmods.dev/badge/skills/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.1 | $0.00035 | $0.00196 |
| Opus 5 | $0.00017 | $0.00098 |
| Sonnet 5 | $0.00007 | $0.00039 |
| Haiku 4.5 | $0.00003 | $0.00020 |
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 4d 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
Wrap-Up
Run two questions in order:
- Confidence audit: What remains unverified or assumption-dependent? For each material item, state why confidence is limited and the exact evidence or test that would resolve it.
- Blind-spot review: What is the single biggest thing the user may be missing? Then name up to three second-order effects or hidden dependencies.
For product or business work, optionally add one unrequested idea only when it is specific, differentiated, and worth its cost or complexity. Name the tradeoff.
Distinguish known facts from hypotheses. Do not manufacture uncertainty, auto-run new work, or treat reflection as approval. Wait for the user to choose which gap, if any, to investigate.
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.
- 4d ago First seen · 22 lines · 35 tokens per session scan A d1d28755a470
wrap-up is a skill published in the GitHub repository rangerrick337/operator-os (10 stars, last pushed 4d ago), licensed MIT. It adds 35 tokens to every session and 196 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
honey-ccr
Compress-cache-retrieve huge array tool output.
a0-development
Development guide for extending Agent Zero from current source and DOX. Use for framework architecture, tools, extensions, API/WebUI handlers, agent profiles, prompts, skills, projects, runtime boundaries, and contribution workflow. Load the focused reference files before giving implementation guidance.
pn-session-handoff
End a session with a structured handoff document and two reflection questions. Captures shipped work, dangling state, resume action, and blind spots. Use via /pn-handoff before closing a session. Pairs with pn-continual-learning for AGENTS.md updates.
claude-session
Find and inspect local Claude Code conversations by session GUID, title, phrase, or recent activity. Use when the user runs /claude-session, asks what Claude Code work they have been doing lately, says a Claude Code conversation died, ran out of context, crashed, or exhausted usage, wants to resume a named…
Send WhatsApp text or media with the local wacli linked-device CLI when the user invokes /whatsapp or explicitly asks to send a WhatsApp message.
pn-context-engineering
Curate what the agent sees and when — rules vs specs vs task files vs errors vs history. Use when starting a session, switching tasks, output quality drops, or the agent ignores project conventions.