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/thewaywithin/agent-11/handoff-notes-movedgit clone --depth 1 https://github.com/TheWayWithin/agent-11Wrote 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/thewaywithin/agent-11/handoff-notes-moved)<a href="https://agentmods.dev/agents/thewaywithin/agent-11/handoff-notes-moved"><img src="https://agentmods.dev/badge/agents/thewaywithin/agent-11/handoff-notes-moved.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.00000 | $0.01320 |
| Opus 5 | $0.00000 | $0.00660 |
| Sonnet 5 | $0.00000 | $0.00264 |
| Haiku 4.5 | $0.00000 | $0.00132 |
Grade A, and why
handoff-notes-moved 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 today.
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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff Notes
For Next Agent: @documenter
Your Immediate Task
What you need to do: Update the GitHub README.md to prominently feature the new Context Preservation System that was implemented in commit a243b02.
Expected outcome: README reflects the major productivity gains from context preservation (87.5% reduction in rework, 37.5% faster workflows) and clearly explains how the system works.
Estimated time: 30-45 minutes
Critical Context You Need
What I Just Completed
- Analysis of Current README: Reviewed entire README.md structure and content
- Context Preservation Research: Found comprehensive system implemented across all agents
- Template Analysis: Verified 3 mandatory context files with complete templates
- Gap Identification: README has NO mention of this major new feature
Important Discoveries
-
Major Feature Missing from README:
- What I found: Context preservation system is fully implemented but completely absent from README
- Why it matters: This is a game-changing feature that addresses the biggest pain point in multi-agent workflows
- Action needed: Add prominent section highlighting this competitive advantage
-
System is Comprehensive and Production-Ready:
- Discovery: All 12 agents updated, templates created, deployment script modified
- Why it matters: This isn't experimental - it's a mature system ready for public promotion
- Action needed: Position this as a key differentiator, not a minor feature
-
Quantifiable Benefits Available:
- Data available: 87.5% reduction in rework, 37.5% faster workflows
- Why it matters: These metrics prove concrete value to users
- Action needed: Lead with the benefits, explain the mechanism second
Current State
- Working: Context preservation system fully implemented and deployed
- Working: All templates created and integrated into deployment script
- Working: README structure and flow is excellent for additions
- Missing: Any mention of context preservation in public-facing documentation
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.
- today First seen · 128 lines · 0 tokens per session scan A 1365ec1b6416
handoff-notes-moved is an agent published in the GitHub repository TheWayWithin/agent-11 (15 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,320 tokens. 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-04.
Other agents, from other repositories
ci-cd-engineer
CI/CD specialist: GitHub Actions, GitLab CI pipelines, deployment automation, build optimization, caching, security scanning.
TASK-CHECKLIST
A long-running agent that plans in prose loses the plan the moment the conversation is summarized. The task checklist keeps the plan out of the message list: it is session state the model edits through three tools and the host reads synchronously — so "did this run actually finish everything?" is a question code can…
dx-engineer
The DX Engineer owns every surface a developer touches -- from the first npm install to the hundredth API call. Its north star: a developer should feel competent, not confused. If they need to read the source code to understand your API, the DX Engineer has failed. If they hit an error and do not know what to do next…
release-agent
Automated release orchestration with quality gates, smoke test integration, and deployment coordination.
ensemble-orchestrator
Chief orchestrator for agent mesh coordination, task delegation, and conflict resolution.
tech-lead-orchestrator
Orchestrate traditional development methodology - plan, architect, task breakdown, develop, code-review, test loop until completion with intelligent delegation and quality loops.