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/conorbronsdon/agent-context-osnpx agentmods add skills/conorbronsdon/agent-context-os/context-updateWrote 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/conorbronsdon/agent-context-os/context-update)<a href="https://agentmods.dev/skills/conorbronsdon/agent-context-os/context-update"><img src="https://agentmods.dev/badge/skills/conorbronsdon/agent-context-os/context-update/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/conorbronsdon/agent-context-os/context-update"><img src="https://agentmods.dev/badge/skills/conorbronsdon/agent-context-os/context-update.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.00039 | $0.00909 |
| Opus 5.5 | $0.00016 | $0.00364 |
| Sonnet 5.5 | $0.00008 | $0.00182 |
| Haiku 4.5 | $0.00004 | $0.00091 |
Grade A, and why
context-update 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 11d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Checkpoint a workspace session
Execution roots (required)
When the host executes commands inside Bash, replace the bash executable
shown below with "$BASH" to reuse that shell. This avoids selecting a different
Bash from PATH, such as the Windows WSL launcher inside a Git Bash session.
In a terminal outside Bash, select the installed Bash explicitly.
Use the exact roots supplied by the host attachment: KernelRoot is the trusted
Context OS product containing scripts/contextos.sh; ContextRoot owns tracked
identity and lifecycle state; and WorkingRoot is the ordinary application.
For an external attachment, require all three exact absolute paths and run:
bash <KernelRoot>/scripts/contextos.sh --context-root <ContextRoot> --working-root <WorkingRoot> <command>
Do not search upward or infer a root from cwd or the skill installation. The
kernel must validate the ignored local binding before strict lifecycle work. A
missing, moved, stale, linked, nested, or mismatched binding stops the workflow;
use the explicit project rebind proposal after a legitimate move. ContextRoot
owns all lifecycle writes. WorkingRoot is read-only evidence. The colocated
bash scripts/contextos.sh <command> compatibility form remains valid.
Throughout this procedure, resolve every context and local-artifact path beneath
ContextRoot. In split mode, spell local paths as absolute <ContextRoot>/...
paths and invoke every lifecycle command through the absolute KernelRoot wrapper
with both exact role options. In colocated mode, run the relative compatibility
commands from the colocated root.
Save continuity with minimal churn through the deterministic lifecycle kernel.
Procedure
- Identify what was completed, any decisions, and whether a priority or open thread changed. Do not invent progress.
- Create a reviewed JSON payload under
<ContextRoot>/.context-os/inputs/withprogressas one to three factual strings. Make each progress entry one self-contained sentence naming its subject and stating one fact; avoid label-prefixed fragments and multiple facts in one sentence, but keep a status and its qualifiers in the same sentence. Apply the same rule to handoff prose. Includecurrent_markdownonly when a priority shifted, a thread opened or closed, or a tracked task completed. When present, it is the complete desired ContextRootcurrent.mdbefore the kernel advances its date and history. Preserve unrelated content and ordering. - Run exactly one matching form:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago Changed · +5 lines 536a0187c3af
- 23d ago Changed 6095abc18475
- 25d ago Changed · +2 lines 3b9bffaa6933
- 1mo ago Changed · +7 lines 82bb01775ebe
- 1mo ago First seen · 61 lines · 39 tokens per session scan A 29d0c890943a
context-update is a skill published in the GitHub repository conorbronsdon/agent-context-os (29 stars, last pushed 5d ago), licensed MIT. It adds 39 tokens to every session and 909 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
journal-optimizer
Guided database pruning and optimization workflows for memory-journal-mcp. Uses importance scores, relationship density, and entry metadata to identify low-value entries for safe soft-deletion. Includes dry-run previews, backup gates, and revert guidance. Use when the user says "clean up the database", "optimize…
mnemo-cortex
Installs and wires Mnemo Cortex (local-first persistent memory) into OpenClaw and other MCP-capable agents. Use for cross-session recall, decision history, or multi-agent shared memory.
kn-init
Use at the start of a new session to read project docs, understand context, and see current state.
kn-extract
Use when extracting reusable patterns, decisions, failures, or knowledge into documentation.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
alive:mine-for-context
Deep context extraction from source material. Creates reference bundles, builds extraction plans, tracks what's been extracted, and discovers new targets — people, subjects, patterns, connections. The archaeologist that turns raw sources into structured knowledge. Can be invoked by alive:session-history for targeted…