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 skills/wrg32786/aigent-os/closenpx skills add wrg32786/aigent-os --skill closegit 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/close)<a href="https://agentmods.dev/skills/wrg32786/aigent-os/close"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/close.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.00015 | $0.02535 |
| Opus 5 | $0.00008 | $0.01267 |
| Sonnet 5 | $0.00003 | $0.00507 |
| Haiku 4.5 | $0.00002 | $0.00253 |
Grade A, and why
close 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 3d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Close
Deprecated. This skill is superseded by [[skills/context-capsule/SKILL.md|/context-capsule]] (docs/two-verb-lifecycle.md). New installs should reach for
/context-capsule; this file stays for anyone still invoking/closeby habit during the transition.
Run the aigent-OS end-of-session memory commit inline. The close must be idempotent: rerunning it after a partial failure must not duplicate ledger entries, capsules, or session summaries.
All operator-owned durable state lives under vault/. Framework indexes such as memory/SKILL_LEDGER.md remain outside the vault and are not session memory.
Hardened compatibility contract
The active two-verb lifecycle does not run a second close ceremony, but manual
/close keeps the same shared postconditions as nightly:
- exact already-authored decision outcomes append only through
daemons/nightly-decision-outcome.mjs, with a unique decision/interval match and compare-and-swap; - bounded Session Log or Active Priorities trimming runs only through
skills/context-hygiene/SKILL.md, archives before removal, and must end inCONTEXT_HYGIENE PASS; - Dream synthesis follows
skills/dream/SKILL.mdand must end inDREAM_CONTRACT PASS; - cognitive changes follow
skills/cognitive-update/SKILL.mdand must end inCOGNITIVE_CONTRACT PASS; - missing canonical input is failure, not "nothing to do";
- judgment-bearing measurement entries are staged through
skills/nightly-ledger-capture/SKILL.md.
These helpers use local memory, Git, stderr, and the SessionStart surface. No external coordination service is required.
Step 0: discipline audit
Run these checks before writing the daily note.
Gate A: honesty ledger
If the session included non-trivial work, completed-task claims, multi-file edits, or consequential decisions and vault/memory/HONESTY_LEDGER.md was not updated:
- Run
/honesty-checkon the most consequential work block. - Append one structured entry covering verified, inferred, guessed, tradeoffs, stopped short, cost implications, self-rating, and resolution.
- Continue only after the entry is durable.
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.
- 3d ago First seen · 298 lines · 15 tokens per session scan A bbdd7161d452
close is a skill published in the GitHub repository wrg32786/aigent-os (17 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 2,535 once invoked, about $0.0001 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-01.
Other skills, from other repositories
gsd-graphify
Build, query, and inspect the project knowledge graph in .planning/graphs/.
hive.note-taking
Maintain a free-form scratchpad of decisions, extracted values, and open questions so context pruning doesn't lose anything you still need.
handoff
Prepare a clean cross-session handoff so the next agent can pick up where you left off. Writes a focused continue.md in the active slice dir and ensures STATE.md + summary artifacts are current. Use when asked to "hand off", "prepare handoff", "pause work", "bookmark this", "I'll come back to this later", before…
user-general-facts
Capture and organize general facts about the user by topic.
02-project-memory
Build the project's memory of its architecture, conventions, and decisions, and wire it into your AI tools. Use when the user wants to set up or refresh project memory, or rewire it into a tool. Not for editing one existing memory file.
project-context
Use PowerContext project memory and handoff tools through MCP when continuing prior work, recalling decisions, maintaining durable memory, or transferring work across tasks, sessions, or agents.