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.
npx skills add escapeboy/ai-prompts --skill ctxgit clone --depth 1 https://github.com/escapeboy/ai-promptsWrote 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/skills/escapeboy/ai-prompts/ctx)<a href="https://agentmods.dev/skills/escapeboy/ai-prompts/ctx"><img src="https://agentmods.dev/badge/skills/escapeboy/ai-prompts/ctx/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/skills/escapeboy/ai-prompts/ctx"><img src="https://agentmods.dev/badge/skills/escapeboy/ai-prompts/ctx.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00051 | $0.01198 |
| Opus 5.5 | $0.00020 | $0.00479 |
| Sonnet 5.5 | $0.00010 | $0.00240 |
| Haiku 4.5 | $0.00005 | $0.00120 |
Grade A, and why
ctx 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 21d 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ctx — Memory & Context Management
Manages the Serena memory system that stores architectural knowledge, conventions, and project context. Loading memories at the start of a session saves 60-70% of tokens by eliminating repeated file reads.
When to Use This Skill (and When NOT to)
| Use this skill for | Use a simpler approach for |
|---|---|
Starting a session on a project with existing memories — load before any code work |
A repo with no memories yet and one quick edit — just read the one file |
Capturing durable architecture / conventions / deploy knowledge that outlives the session (save, create) |
An ephemeral session fact — let auto-memory / MEMORY.md hold it |
| Refreshing a memory after a major refactor so Claude stops making stale assumptions | A memory touched days ago on an unchanged codebase — it's still current |
Auditing what's loaded and what caching is buying you (inspect, list) |
A single-file lookup where symbolic exploration answers it directly |
Start simple. Reach for this skill only when the project has (or clearly warrants) reusable
memories — don't scaffold a memory set for a one-off task. Without Serena, use
/optimize instead; it has fallback strategies.
Usage
/ctx [action] [name]
Quick Examples
/ctx load # Load all relevant memories for current project
/ctx list # Show all available memories
/ctx save architecture # Create or update the architecture memory
/ctx refresh codebase-conventions # Regenerate a stale memory
/ctx inspect # Show what's currently loaded + cache status
/ctx clear # Unload all memories from context
Actions
Compact dispatch below. For the full process steps, parameters, and output formats of any action, read references/actions.md.
| Action | What it does | When to run |
|---|---|---|
load |
Load core memories (architecture, codebase-conventions) + conditionally load module/testing/docker/deployment memories by task context |
Start of every session, before code work |
list |
List all project memories with last-updated + load/cache status | To see what's available |
save [name] |
Gather context → structure as Markdown → write .serena/memories/[name].md |
After learning something durable worth persisting |
refresh [name] |
Re-explore the code and overwrite an existing memory with current state | After a major refactor, a new module, or a memory >2 weeks old |
inspect |
Show loaded memories, token sizes, cache hit rate, and project/Serena/constitution status | To audit context + caching |
clear |
Unload all memories from the current conversation (does not delete files) | Switching projects or context is stale |
create [name] |
Interactive memory creation — asks what to document and how to structure it | When you want to build a memory step by step |
What ships with it
3 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.
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.
- 21d ago First seen · 109 lines · 51 tokens per session scan A af190d390325
ctx is a skill published in the GitHub repository escapeboy/ai-prompts (91 stars, last pushed 9d ago), licensed MIT. It adds 51 tokens to every session and 1,198 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-09-25.
Other skills, from other repositories
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…
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…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
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.
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…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.