Spend less on coding agents. Control what they do.

London, England
Joined May 2026
Your team wrote great agent skills. They live on one laptop. Import them into Context Mode from GitHub once. The right skill loads itself when your message needs it, on every machine. When you are just chatting, none loads.
1
1
2
4
499
Context Mode retweeted
Replying to @contextmode
@contextmode is #3 on GitHub Trending today! Thank you to everyone contributing code, reporting issues, and spreading the word.🫡
4
1
18
1,386
Someone built a plugin that cuts AI coding token usage by up to 98% Context Mode filters massive tool outputs before they reach your agent, reducing context waste while preserving searchable session memory across long coding tasks. Setting up in Claude Code: 1. /plugin marketplace add mksglu/context-mode 2. /plugin install context-mode@context-mode 3. Restart and run /context-mode:ctx-doctor to check the hooks are live Repo: github.com/mksglu/context-mo…
26
16
173
78,985
Every @contextmode account starts with the same default rules: ASD-STE100, the controlled English of aircraft maintenance manuals. Plus Orwell's 6 rules from 1946. Short answers. No wall of text. Code and terms stay exact. Write your own once. Every agent follows them.
1
2
3
545
Context Mode retweeted
Yeah, it’s the same idea as a PreToolUse hook but it doesn’t live in the client. Protect sits on the request path, sees every call from Claude Code and Codex before it runs, strips wrappers like sudo or sh -c, and blocks based on what the call actually does. Blocked calls never reach the shell. Local hooks are easy to miss or bypass. This is one policy at the gateway for both agents on every machine. @contextmode
Replying to @mksglu @contextmode
Is it something like Claude code PreToolUse hook
3
1
3
304
Rough one, glad prod was safe. The part that stuck with me: the agent "saved a rule for itself." That rule lives inside the model. We put ours one hop before the command runs, so a destructive migration needs your OK first, not an apology after.
This is exactly why we built @contextmode Protect. The model said it best: "I saved a rule for myself." A rule the model keeps for itself is a suggestion. Protect puts the rule outside the model. Commands like `prisma migrate`, `DROP`, `db reset` or anything touching production get checked before they run, whatever the agent decides. Your agent can be sorry. Or it can be stopped.
3
235
Long coding sessions fill the context window, and the agent compacts at a moment you didn't choose. Early decisions get lost. Active Context turns that into a setting. Pick a limit once (200K, 500K or 1M). Context Mode keeps every thread under it and archives older turns word for word, so nothing is lost and your own messages are never shortened. One setting covers every agent and every machine.
1
1
1
4
594
Ask your coding agent about a big data file and it pastes the whole file into the prompt. You pay for every byte. Thinking in Code flips it: the agent writes a short script, the script reads the file, and the model only sees the answer. 64% lower cost on Claude Haiku 4.5. Same correct answers. context-mode.com/thinking-in…
1
2
4
717
Your coding agent talks to the model with nobody in between. We put one @Cloudflare Worker in the middle: → it folds big tool output before you pay for it → it remembers across Claude, Codex and machines → it stops risky commands before they run Dynamic Workers, Durable Objects, Workers AI, Containers. One hop. Watch the whole machine run 👇
1
1
5
719
A coding agent starts each session with what its client loads, and nothing more. Memory in @contextmode takes short facts from your turns, stores each one with two clocks (when it was true, and when we learned it), and adds only the facts that matter to the first request of a new conversation, in Claude Code and Codex. In an offline eval, memory tokens per new conversation fell from 262 to 41, and the share of relevant facts rose from 4.2% to 45.3%. context-mode.com/blog/memory…
2
1
4
151
A text model used to make them, and it was often wrong and sometimes very slow. We moved four of these choices to @CloudflareDev (cc: @michellechen) Clef decision models, measured each move, and shipped three. In an offline test, the right skill fired 9 or 10 times in 10 instead of 4, and memory sent 41 tokens per opening instead of 262. context-mode.com/blog/why-we…
1
2
160