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 manager-dot-dev/manager-skills --skill em-contextgit clone --depth 1 https://github.com/manager-dot-dev/manager-skillsWrote 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/manager-dot-dev/manager-skills/em-context)<a href="https://agentmods.dev/skills/manager-dot-dev/manager-skills/em-context"><img src="https://agentmods.dev/badge/skills/manager-dot-dev/manager-skills/em-context/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/manager-dot-dev/manager-skills/em-context"><img src="https://agentmods.dev/badge/skills/manager-dot-dev/manager-skills/em-context.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.00095 | $0.01452 |
| Opus 5.5 | $0.00038 | $0.00581 |
| Sonnet 5.5 | $0.00019 | $0.00290 |
| Haiku 4.5 | $0.00010 | $0.00145 |
Grade A, and why
em-context 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 1mo 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EM Context
This is the foundation skill. Its purpose is to capture your team, org, and individual direct report context so every other skill can work with your specific situation rather than generic advice.
This skill is not meant to be the main thing you invoke every day. It is the shared memory layer for the other EM skills.
File Structure
.agents/
├── em-context.md # Your team and org context
└── reports/
├── alice.md # One file per direct report
├── bob.md
└── carol.md
How to Use
Team context: Create .agents/em-context.md with your team and org context. All EM skills read this first.
Direct report profiles: Create .agents/reports/[firstname].md for each direct report. Skills like 1on1s, feedback, and performance-reviews will look for this file when you mention a person by name.
If files don't exist, ask the user for the relevant context before proceeding.
When other skills learn durable new context, they should update these files automatically. Treat them as living memory, not static setup files.
Bootstrapping Missing Context
If there is no .agents/em-context.md yet, do not keep giving generic advice forever. Ask for a minimal manager profile first, create the file, and then continue.
Minimum manager profile to collect:
- role/title
- team size
- team mission or area of ownership
- current challenge or priority
If a specific person comes up and there is no .agents/reports/[name].md yet, ask for a minimal profile for that person first, create the file, and then continue.
Minimum direct report profile to collect:
- title or level
- tenure on the team
- strengths
- current challenge, growth area, or reason they came up
Do not wait for a perfect profile. Save the minimum useful context first, then enrich it over time as new conversations reveal more.
Auto-Update Rules
All EM skills should use em-context as shared memory:
- Read
.agents/em-context.mdfirst if it exists - If a specific person is involved, also read
.agents/reports/[name].md - If
.agents/em-context.mddoes not exist, collect the minimum manager profile and create it before giving detailed advice - If a specific person is involved and
.agents/reports/[name].mddoes not exist, collect the minimum direct report profile and create it before giving detailed advice - If the conversation reveals durable new context, update the relevant file automatically
- Prefer additive updates over rewrites
- Do not overwrite existing context unless the user clearly corrected it
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.
- 1mo ago First seen · 196 lines · 0 tokens per session scan A b598d5cd93ac
em-context is a skill published in the GitHub repository manager-dot-dev/manager-skills (115 stars, last pushed 5mo ago), licensed MIT. It adds 95 tokens to every session and 1,452 once invoked, about $0.0004 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-08-30.
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…
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…
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.
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.