context-management

context-management is a skill for Claude Code, Codex from implicit-labs/autosymph. It costs 56 tokens per session (2,005 once invoked), scanned A, original, MIT.

A set of practices for protecting large data during long coding-agent sessions. It covers files such as screenshots, videos, base64 data, JSON, and lengthy test output.

In plain words
What is it for?
It helps pass large artifacts between turns, manage long test runs, and keep session data reliable.
Why use it?
It prevents context limits or compression from silently changing data and producing corrupt uploads or incomplete results.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code.

Good fit It helps pass large artifacts between turns, manage long test runs, and keep session data reliable.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/implicit-labs/autosymph/context-management
Install

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.

Any agent
npx skills add implicit-labs/autosymph --skill context-management
Clone the repo
git clone --depth 1 https://github.com/implicit-labs/autosymph

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for context-management

README.md
[![agentmods](https://agentmods.dev/badge/skills/implicit-labs/autosymph/context-management/github.svg)](https://agentmods.dev/skills/implicit-labs/autosymph/context-management)
Your own site
<a href="https://agentmods.dev/skills/implicit-labs/autosymph/context-management"><img src="https://agentmods.dev/badge/skills/implicit-labs/autosymph/context-management/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.

agentmods 80×15 button for context-management

Your own site · 80×15
<a href="https://agentmods.dev/skills/implicit-labs/autosymph/context-management"><img src="https://agentmods.dev/badge/skills/implicit-labs/autosymph/context-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,005 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00056 $0.02005
Opus 5.5 $0.00022 $0.00802
Sonnet 5.5 $0.00011 $0.00401
Haiku 4.5 $0.00006 $0.00200

Measured 2mo ago against content hash 1ba52d9b4700, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

context-management 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 2mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (test.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/context-management/SKILL.md · 199 lines

How it starts

The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Context Management for Long-Running Agents

Prevent context compaction from silently corrupting your data. This skill teaches three layers of defense: file-based handoff, size awareness, and context threshold management.

When to Use

  • During verify runs that capture multiple screenshots or videos
  • When base64-encoding files for Linear upload
  • When test output exceeds a few hundred lines
  • When a session is running long (35+ turns)
  • When tool results start showing "persisted to disk" messages
  • Any time you hold large data in context across API turns

Layer 1: File-Based Handoff

The core rule: Never hold large data in context across API turns. Write it to disk, then read it back in the SAME turn you need it.

Context compaction triggers at ~80% window fill. Any data in older turns is fair game for truncation — silently. You won't get a warning. Your 18,984-char base64 becomes 8,498 chars and the upload produces a corrupt file.

Pattern: Write → Read-in-Same-Turn → Consume

# Step 1: Generate data and write to disk (ONE Bash call)
sips -Z 800 -s format jpeg input.png --out output.jpg 2>/dev/null && \
  base64 -i output.jpg > output.b64 && \
  wc -c < output.b64

# Step 2: Read file back (in the SAME response as Step 3)
cat output.b64

# Step 3: Consume immediately (SAME API turn as Step 2)
mcp__linear__create_attachment(
  issue: "ISSUE-XXX",
  base64Content: <content from cat>,
  filename: "output.jpg",
  contentType: "image/jpeg",
  title: "Description"
)

Steps 2 and 3 MUST be in the SAME response. If they're in different API turns, context compaction may truncate the base64 between them.

When to Use Files vs Inline

Data Type Size Action
Base64 (any) >10K chars Write to .b64 file
Base64 (any) <10K chars OK inline if consumed same turn
JSON payload >50 lines Write to .json file
Test output >200 lines Pipe to file: swift test 2>&1 | tee test-output.txt
Screenshot PNG Any Always resize first (see Size Thresholds)
Video Any Always file-based (too large for context)
Git diff >100 lines Write to file, read relevant sections

Read the full file on GitHub · 199 lines

Files

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.

Changes

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.

  1. 2mo ago First seen · 199 lines · 56 tokens per session scan A 1ba52d9b4700

Subscribe to this mod's changes

context-management is a skill published in the GitHub repository implicit-labs/autosymph (5 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 2,005 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-31.

Related

Other skills, from other repositories

knowledge-ingest

Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, source notes, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…

openclaw/openclaw · 80 tokens

forget

Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…

asgeirtj/system_prompts_leaks · 74 tokens

mem0-oss-to-platform

Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…

mem0ai/mem0 · 217 tokens

Cortex

LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…

danielmiessler/LifeOS · 184 tokens

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.

opensquilla/opensquilla · 44 tokens

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…

shiwenwen/hope-agent · 115 tokens