context-engineering

A method for managing the information an AI coding agent sees during a session. It covers writing, selecting, compressing, and isolating context to fit token limits.

In plain words
What is it for?
Use it to plan what the agent should remember, reduce unnecessary context, and separate information between tasks.
Why use it?
Long sessions can become slower or less accurate when too much information is carried forward. Managing the context keeps the useful details available within the session limit.

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/rohitg00/pro-workflow/context-engineering
Any agent
npx skills add rohitg00/pro-workflow --skill context-engineering
Clone the repo
git clone --depth 1 https://github.com/rohitg00/pro-workflow

Made for: Claude Code, Codex.

Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,401 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin unknown 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.00041 $0.01401
Opus 5 $0.00020 $0.00700
Sonnet 5 $0.00008 $0.00280
Haiku 4.5 $0.00004 $0.00140

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

Security

Grade B, and why

context-engineering scanned grade B with 1 finding 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

"command": "cat .claude/critical-context.md"
skills/context-engineering/SKILL.md · 158 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 158 lines · 41 tokens per session scan B 0bdccd0fb26b

Subscribe to this mod's changes

context-engineering is a skill published in the GitHub repository rohitg00/pro-workflow (2,799 stars, last pushed yesterday), with no licence file. It adds 41 tokens to every session and 1,401 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.