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 wrg32786/aigent-os --skill envelopegit clone --depth 1 https://github.com/wrg32786/aigent-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/wrg32786/aigent-os/envelope)<a href="https://agentmods.dev/skills/wrg32786/aigent-os/envelope"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/envelope/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/wrg32786/aigent-os/envelope"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/envelope.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00070 | $0.01027 |
| Opus 5.5 | $0.00028 | $0.00411 |
| Sonnet 5.5 | $0.00014 | $0.00205 |
| Haiku 4.5 | $0.00007 | $0.00103 |
Grade A, and why
Envelope 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 1mo 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Envelope
Sort an incoming request into one of three envelopes — A: Ship, B: Ask one focused question, C: Propose first — and act accordingly.
When to use
- The principal gives a directive and you're tempted to respond with multiple clarifying questions
- The work involves a fork in the road and you're tempted to present multiple options
- Before posting any "should I…?" question
- Triggered by Caddy on prompts like: "should I", "before I start", "is this clear", "is this OK", "couple options", "two paths", "ambiguous", "not sure if you want", "want me to", "ship vs ask", "decision tree", "fork in the road"
The decision tree (run top-to-bottom)
1. Is the request unambiguous?
YES → step 2
NO → can I resolve the ambiguity by reading code/data/docs?
YES → resolve, then step 2
NO → ENVELOPE B: ask exactly one focused question with options spelled out
2. Is the change reversible?
YES → step 3
NO → is the irreversibility expensive? (data loss, schema migration, deploy, broken contract)
YES → ENVELOPE C: propose first, wait for sign-off
NO → step 3
3. Is the change bounded to a known surface area?
YES → step 4
NO → can I re-scope to a bounded version?
YES → propose the bounded version + ship that
NO → ENVELOPE C: propose first
4. Do I have full context to make the change correctly?
YES → ENVELOPE A: SHIP
NO → load missing context (search/read/query); re-evaluate
5. After shipping: did verification pass?
YES → declare done with summary
NO → loop back to step 4 (more context, different approach)
Envelope rules
Envelope A — Ship it
- Clear request, known surface, reversible, low rollback cost
- Action: just do it. Do not ask "should I proceed?" after permission was already given. Asking permission for things you've been authorized to do wastes the principal's attention.
Envelope B — Ask exactly one focused question
- 2+ reasonable interpretations that produce meaningfully different outcomes
- Cannot resolve by reading code/data
- Action: one surgical question with options spelled out. Not "what do you want?" — "do you want X or Y? Consequences are A vs B."
- Never ask a question you can answer yourself by reading the code.
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.
- 1mo ago First seen · 105 lines · 70 tokens per session scan A 963b2f42a927
Envelope is a skill published in the GitHub repository wrg32786/aigent-os (23 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 1,027 once invoked, about $0.0003 per session on Opus 5.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-01.
Other skills, from other repositories
nav-pilot
Dispatch a Navigator task doc to Pilot as a labeled GitHub issue. Use when user says "dispatch TASK-XX to Pilot", "hand off to Pilot", "send to Pilot", or "queue for Pilot". One-way handoff (Navigator authors the spec, Pilot executes autonomously).
graphify
Use when the user invokes /graphify or asks to build, update, or query a knowledge graph from a folder of files (code, docs, papers, notes, images). Triggers: 'map this codebase', 'graph my notes', 'what is connected across these files', 'community detection', 'GraphRAG', incremental graph update, Neo4j/SVG/GraphML…
insights
Use when the user types /weekly or /monthly, asks for a weekly or monthly journal review or retrospective, asks 'how was my week' or 'how was my month', or wants trends, anomalies, or patterns across recent journal entries. Also fires when regenerating an insight report for a past week or month. NOT for writing…
setup-brain
Set up or upgrade an AI-powered Obsidian vault. Interviews you, builds your vault structure (or works with what you already have), creates your CLAUDE.md memory file, installs tools, and gets you journaling — all in one conversation. Also has a repair/upgrade path for existing users.
second-brain-mapping
Use when the user wants to map or remap their second brain, refresh the vault's queryable metadata index, extract structured frontmatter from typed notes (books, meetings, people, journals, goals), fill wikilink gaps, or surface cross-type insights and patterns no single file shows. Triggers: /second-brain-mapping…
sunday-review
Use when the user asks for the weekly meta-review or Sunday wrap-up of their week and vault: says /sunday, /sunday-review, 'let's do the weekly review,' 'Sunday review,' 'review my week,' 'weekly retro,' 'week in review,' 'end-of-week review,' or wants journals, patterns, vault health, and stale decisions reviewed…