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/conorbronsdon/agent-context-os/context-updatenpx skills add conorbronsdon/agent-context-os --skill context-updategit clone --depth 1 https://github.com/conorbronsdon/agent-context-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/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.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.00039 | $0.00781 |
| Opus 5 | $0.00019 | $0.00391 |
| Sonnet 5 | $0.00008 | $0.00156 |
| Haiku 4.5 | $0.00004 | $0.00078 |
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 2d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Checkpoint a workspace session
Execution roots (required)
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. 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:
split: bash <KernelRoot>/scripts/contextos.sh --context-root <ContextRoot> --working-root <WorkingRoot> propose update --input <ContextRoot>/.context-os/inputs/<payload.json> colocated: bash scripts/contextos.sh propose update --input .context-os/inputs/<payload.json>
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.
- 2d ago Changed · +7 lines 82bb01775ebe
- 4d 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 (21 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 781 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-08-30.
Other skills, from other repositories
next-cache-components
Next.js 16 Cache Components guidance. Use when refactoring React Server Components for performance, debugging Partial Prerendering (PPR) issues, or applying the use cache directive, cacheLife, cacheTag, updateTag, and revalidateTag. Also use when deciding whether data should be static, cached, or dynamic, or when…
agents-sdk
Build AI agents on Cloudflare Workers using the Agents SDK or build Model Context Protocol (MCP) servers. Load when creating stateful agents, durable workflows, MCP servers, checking MCP schema/error responses, or reviewing MCP code quality. Covers Agent class, state management, callable RPC, Workflows integration…
github-actions
Master GitHub Actions CI/CD workflows with production-grade security and performance patterns. Use ONLY when explicitly setting up CI/CD pipelines specifically via GitHub Actions, setting up matrix strategies, caching dependencies, managing artifacts, or implementing reusable workflows. For deployment requests, use…
python
Master modern Python development with production-grade tooling and idioms. Use when writing Python code, configuring project structure, managing dependencies with uv, linting with ruff, adding type hints, writing pytest tests, or building FastAPI/Django/Flask applications. Triggers on "Python", "FastAPI", "Django"…
tailwind-css
Master Tailwind CSS v4 with its CSS-first configuration paradigm. Use when writing utility classes, configuring design tokens via @theme, implementing dark mode, migrating from v3, or integrating with React/Vue/Svelte. Triggers on "Tailwind", "utility CSS", "Tailwind v4", "@theme", "dark mode classes", "responsive…
workers-best-practices
(APPLICATION CODE ONLY) Reviews and authors Cloudflare Workers code against production best practices. Use ONLY when writing or reviewing Worker code, configuring wrangler.jsonc, or checking for anti-patterns. Do NOT use for general Cloudflare product discovery (use cloudflare instead) or CLI management (use wrangler…