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.
git clone --depth 1 https://github.com/tobihagemann/turboWrote 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/plugins/tobihagemann/turbo/context-level)<a href="https://agentmods.dev/plugins/tobihagemann/turbo/context-level"><img src="https://agentmods.dev/badge/plugins/tobihagemann/turbo/context-level/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.
<a href="https://agentmods.dev/plugins/tobihagemann/turbo/context-level"><img src="https://agentmods.dev/badge/plugins/tobihagemann/turbo/context-level.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
context-level 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 11d 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.
What it actually says
{
"name": "context-level",
"version": "0.1.0",
"description": "Gives Claude a tool that reads how much of the context window remains.",
"author": {
"name": "Tobias Hagemann"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 47 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 11d ago First seen · 9 lines scan A b2974dd43f08
context-level is a plugin published in the GitHub repository tobihagemann/turbo (409 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-10-03.
Other plugins, from other repositories
agent-tooling
Agent Tooling — Building the skills, hooks, commands, and plugins that agents run on.
working-memory
A project's mid-term memory: a WORKING.md file in the repo that holds the current stage's state — decision log, dead ends, next steps — so it survives context compaction and new sessions, and gets distilled into long-term memory at stage end.
office-memory
Manual V1 Lite method for AI-curated daily, current, and durable project memory.
lore
Persistent project knowledge base for Claude Code. Records current state, phased roadmap, decisions and their rejected alternatives, and failed approaches — so a new session resumes from what was recorded instead of re-reading the whole codebase.
my-adhd-caveman
ADHD-friendly structure plus caveman diction: action first, numbered terse steps, fewer tokens.
context-degradation
Patterns for recognizing and mitigating context failures in LLM agents. Covers lost-in-middle, context poisoning, distraction, confusion, clash, and model-agnostic degradation measurement.