context-engineering

A set of methods for controlling the information an AI agent receives, keeps, retrieves, shortens, and separates during a task.

In plain words
What is it for?
Use it to organize persistent instructions, retrieve relevant project knowledge, shorten context, allocate context space, and keep separate agents from sharing unrelated information.
Why use it?
It helps prevent agents from losing focus or instructions when their context becomes too long, and can reduce the amount of text sent to language models.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/bdiasti/maestro-bundle-cli/context-engineering
Any agent
npx skills add bdiasti/maestro-bundle-cli --skill context-engineering
Clone the repo
git clone --depth 1 https://github.com/bdiasti/maestro-bundle-cli

Made for: Claude Code, Codex.

Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,465 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00042 $0.01465
Opus 5 $0.00021 $0.00732
Sonnet 5 $0.00008 $0.00293
Haiku 4.5 $0.00004 $0.00146

Measured 2d ago against content hash 9210313d3bfb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

context-engineering 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.

templates/bundle-ai-agents/skills/context-engineering/SKILL.md · 167 lines

How it starts

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

Context Engineering

Apply the four context engineering strategies -- Write, Select, Compress, Isolate -- to maximize agent effectiveness while minimizing token costs.

When to Use

  • Designing what context an agent receives before execution
  • Optimizing a system prompt that is too long or unfocused
  • Reducing token costs on expensive LLM calls
  • Setting up context isolation between agents in a multi-agent system
  • Debugging an agent that "forgets" instructions or loses focus

Available Operations

  1. Write persistent context (CLAUDE.md, agents.md, skills)
  2. Select relevant context via retrieval
  3. Compress context to reduce token usage
  4. Isolate context per agent scope
  5. Budget context allocation across the window

Multi-Step Workflow

Step 1: Write Context -- Persistent Memory

Define what the agent "knows" before any task begins. This is your baseline context layer.

CLAUDE.md          -> Project standards, architecture, decisions
agents.md          -> Agent-specific behavior and role definition
skills/SKILL.md    -> On-demand capabilities loaded when needed
memory/            -> Learnings from previous executions

Check your CLAUDE.md token count:

wc -w CLAUDE.md  # Should be under ~1500 words (~2000 tokens)

Rule: CLAUDE.md must stay under 2000 tokens. If it grows beyond that, move details into skills that are loaded on-demand.

Step 2: Select Context -- Retrieval for the Current Task

Inject only the context relevant to the current task. Never dump everything.

def select_context(task: Task, retriever) -> str:
    # Retrieve skills relevant to the task
    relevant_skills = retriever.invoke(task.description)

    # Search for related code in the repository
    related_code = code_search(task.description, worktree_path)

    # Find similar past decisions
    past_decisions = memory_store.search(task.description, k=3)

    return format_context(relevant_skills, related_code, past_decisions)

Rule: Never inject more than 30% of the context window with selected context. Leave space for the agent to reason.

Read the full file on GitHub · 167 lines

Files

What ships with it

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

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. 2d ago First seen · 167 lines · 42 tokens per session scan A 9210313d3bfb

Subscribe to this mod's changes

context-engineering is a skill published in the GitHub repository bdiasti/maestro-bundle-cli (21 stars, last pushed 5mo ago), licensed MIT. It adds 42 tokens to every session and 1,465 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.