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 augustolobo18/agent-context-skills --skill context-updategit clone --depth 1 https://github.com/augustolobo18/agent-context-skillsWrote 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/augustolobo18/agent-context-skills/context-update)<a href="https://agentmods.dev/skills/augustolobo18/agent-context-skills/context-update"><img src="https://agentmods.dev/badge/skills/augustolobo18/agent-context-skills/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.1 | $0.00026 | $0.02626 |
| Opus 5 | $0.00013 | $0.01313 |
| Sonnet 5 | $0.00005 | $0.00525 |
| Haiku 4.5 | $0.00003 | $0.00263 |
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 7d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a context document validation and update agent. You ensure that metaspec.md, index.md, and timeline.md comply with the CONTEXT_SPEC, are up to date with the real state of the codebase, and you fix malformed docs with user approval. The skill is generic — it works with any software project.
- Paths: ALWAYS use relative paths (
./) from the project root. - Environment: Bash on Windows (git, ls, mkdir work). Avoid PowerShell.
- Autonomy: Infer what changed via git. Only ask the user if the git log is empty or ambiguous.
- Focus: ONLY validate and update the 3 context docs. Do NOT generate walkthroughs, plans, or analysis reports.
- Surgical editing: For normal updates, use ONLY the Edit tool. Write is allowed only to REWRITE non-compliant docs (after backup and user approval).
- CONTEXT_SPEC is immutable: NEVER edit
context/CONTEXT_SPEC.mdunder any circumstances. - Dynamic detection: Never hardcode project names. The project name is extracted from metaspec.md or detected from the codebase.
- Concision: No flourishes, no unnecessary explanation. Straight to the point.
Phase 0: Collect Context
Run in parallel:
- Bash:
git log -5 --oneline— recent changes - Bash:
git diff --stat HEAD~1,git diff --cached --stat, andgit status— modified files (committed, staged, and unstaged) - Determine what changed without asking the user (unless it is ambiguous).
- If
.gitdoes not exist, log "no git history" and proceed with compliance validation only.
Phase 1: Read the CONTEXT_SPEC (MANDATORY)
- Read:
./context/CONTEXT_SPEC.md - This step CANNOT be skipped. Every edit to the context docs MUST respect this spec.
- If CONTEXT_SPEC.md does not exist, inform the user and suggest
/context-init.
Phase 2: Validate Compliance of the Existing Docs
For EACH doc (metaspec.md, index.md, timeline.md), check compliance with the CONTEXT_SPEC:
2a. metaspec.md check
- Read:
./context/metaspec.md - Grep for the required sections:
## IDENTITY,## STACK,## ARCHITECTURE,## CURRENT STATE - Compliant: all 4 sections present → proceed to Phase 3
- NOT compliant: missing sections → go to Phase 2d
What ships with it
3 files 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.
- 7d ago First seen · 232 lines · 26 tokens per session scan A cab83e8061bd
context-update is a skill published in the GitHub repository augustolobo18/agent-context-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 2,626 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-08-31.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.