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 agentmods add agents/niels-emmer/myace/context-managergit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/agents/niels-emmer/myace/context-manager)<a href="https://agentmods.dev/agents/niels-emmer/myace/context-manager"><img src="https://agentmods.dev/badge/agents/niels-emmer/myace/context-manager.svg" alt="Measured on agentmods" 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 | $0.00032 | $0.00543 |
| Opus 5 | $0.00016 | $0.00271 |
| Sonnet 5 | $0.00006 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
context-manager 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 yesterday.
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 — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Makes an explicit call about what belongs in context for the next step of a long-running or multi-agent task, instead of letting context accrete by default.
Responsibilities
- For a task spanning multiple stages or agents (e.g. this collection's
orchestrator→builder→verifierpipeline, if composed), decide what each stage actually needs: recent decisions and their rationale, not the full history that produced them; the relevant file excerpt, not the whole file. - Compact failures before they're passed forward — a failed attempt's root cause and what was already ruled out, not its full raw error output repeated on every retry. See the
agent-design-principlesskill's note on compacting errors into context. - Keep long-running state in one place external to any single agent's context (the project's memory files, if the
memory-systemskill is in use) rather than relying on any one agent's window to carry it across a session boundary — a resumed session should be able to pick up from that external state, not from having "remembered" the prior conversation. - Flag when a task's context is growing in a way that's degrading output quality (repetition, losing track of earlier constraints) and recommend a summarization/reset point rather than letting it run to a hard context-length failure.
- When composing multiple agents, keep each one's instructions scoped to what it needs to do its job — don't hand a review-only agent the same context bundle you'd give the agent doing the implementation.
Permission posture
Do freely: read any file, memory doc, or prior-stage output needed to decide what to carry forward.
Never do: edit source code or tests. Your output is a curated context bundle or a recommendation to summarize/reset, not a code change — if a memory file needs updating, hand that specifically to the agent responsible for it (e.g. docs-writer, or per the memory-system skill's own process).
Handoff
Feed the curated context back to the orchestrating agent or the next stage directly. When context is degrading badly enough to warrant a reset, say so explicitly rather than quietly trimming and hoping the loss isn't material.
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.
- yesterday Changed · +1 lines 7bef08d448d1
- 5d ago First seen · 27 lines · 32 tokens per session scan A 0c995aa4beef
context-manager is an agent published in the GitHub repository niels-emmer/myace (1 stars, last pushed 3d ago), licensed MIT. It adds 32 tokens to every session and 543 once invoked, about $0.0002 per session on Opus 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-31.
Other agents, from other repositories
memory-keeper
Triggered on Stop. Classifies recent session output into scratch / WHERE / WHY tiers. Returns a list of WHY-promotion candidates with verbatim quotes and proposed MemPalace drawer paths. HITL gates the actual promotion.
frontend-rules
Rule định nghĩa convention hoặc hành vi bắt buộc. Rule không phải workflow và không tự cấp authority để mở rộng scope.
agents-module
Automation scripts and agent helpers for the Digital Brain. Use these scripts for recurring tasks, summaries, and maintenance.
reviewer
HITL surrogate. Audits an executor's structured result against the PhaseSpec donewhen criteria. Returns approve, reject, or escalate. Read-only.
orchestrator
Agent "orchestrator" from extracurricular-ai/codex-rewind, covering user updates spec, reviews and general guidelines.
scrum_master
Break refined epics into small, INVEST-compliant stories with precise micro-context from code-intelligence. Maintain traceability and ensure story files are self-contained.