Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/wrg32786/aigent-osnpx agentmods add skills/wrg32786/aigent-os/openWrote 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/open)<a href="https://agentmods.dev/skills/wrg32786/aigent-os/open"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/open/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/open"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/open.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 5 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 10 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00016 | $0.00945 |
| Opus 5.5 | $0.00006 | $0.00378 |
| Sonnet 5.5 | $0.00003 | $0.00189 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
open 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Open
Deprecated. This skill is superseded by [[skills/resume/SKILL.md|/resume]] (docs/two-verb-lifecycle.md). New installs should reach for
/resume; this file stays for anyone still invoking/openby habit during the transition.
Run this at the start of every normal working session.
Nightly alert surface
Before normal orientation, run the local watchdog with the same configured time zone and cutoff used by the pass:
node daemons/nightly-watchdog.mjs --root <aigent-root>
Surface every active named alert from
vault/memory/runtime/NIGHTLY_ALERTS.jsonl. The append-only ledger and stderr
are the default delivery channels; no external coordination service is
required. If the ledger is unreadable, report ALERT_LEDGER_INVALID and
continue the resume path. An alert-read failure must never suppress session
orientation or make the hook indistinguishable from "not installed."
First-run detection
Before the normal protocol, read .aigent/state.json.
- If
statusis notready, run/startinstead of the normal open protocol. - If the JSON state is missing but
.aigent/first-run-doneexists, treat the installation as ready and create the JSON state as a compatibility migration. - Do not inspect natural-language placeholders in
system/00_identity.md. Product state belongs in machine-readable state, not in whether a sentence happens to survive an edit.
Protocol
Unbanked-session recovery: Compare .aigent/last-close, if present, with the newest Session Captures in vault/daily/. If newer captures exist, recover a short summary into vault/memory/SESSION_LOG.md, mark it (auto-recovered), and continue. State the recovery in one neutral line.
- Load the heat index from
vault/memory/HEAT_INDEX.jsonwhen present. Usehot_top_20as the prioritized reading list. If missing, use steps 2 through 6 normally. - Read the latest daily note in
vault/daily/. - Read the session log at
vault/memory/SESSION_LOG.mdand extract the newest next action and open threads. - Read active priorities at
vault/memory/ACTIVE_PRIORITIES.md. - Follow the graph from the latest daily note and open threads into the three to five most relevant project, concept, person, or agent notes.
- Check delegation at
vault/memory/DELEGATION_TRACKER.mdfor blocked, stale, or review-ready work. - Decision aging: compare
vault/memory/DECISION_LOG.mdandvault/memory/DECISION_OUTCOMES.md. Surface at most three unresolved decisions around 30, 60, or 90 days old. - Attention reconciliation: compare the last seven days in
vault/daily/with intended focus invault/memory/ACTIVE_PRIORITIES.md. Surface material drift only. - Skill gap scan: once per week, inspect
memory/SKILL_GAPS.md. If an open gap is older than seven days, run/skill-hunton the oldest one and update the ledger if resolved. - Compute runtime state:
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 · 71 lines · 16 tokens per session scan A aef8fe0ba0f4
open is a skill published in the GitHub repository wrg32786/aigent-os (24 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 945 once invoked, about $0.0001 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
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…
evolve
Use when many related hardened instincts (high-confidence feedback/discovery memories) have piled up in one domain, when the user runs /evolve or asks to promote, cluster, graduate, or consolidate accumulated instincts into a Command, Skill, or Agent, or when files in Instinct Proposals need review. Part of the…
vault-system
Use when maintaining the vault ITSELF as a system, not its content: knowledge-graph build/rebuild/query (graphify), second-brain mapping, vault diagnose/audit/hygiene, drift detection, extract rules from vault, backfill journals, setup vault types, consolidate memory (index over cap), Obsidian tooling…
diagnose
Use when an AI Brain vault needs a health check or something feels off: Claude ignores CLAUDE.md, journal entries missing from /weekly, hooks not firing, something broke after a git pull, a friend's install misbehaves, Obsidian crashes or pegs the CPU, a .claude/worktrees folder appeared, Granola/WhatsApp/Slack/Gmail…
nav-compact
Clear conversation context while preserving knowledge via context marker. Use when user says "clear context", "start fresh", "done with this task", or when approaching token limits.