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 romiluz13/cc10x --skill memory-and-handoffgit clone --depth 1 https://github.com/romiluz13/cc10xWrote 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/romiluz13/cc10x/memory-and-handoff)<a href="https://agentmods.dev/skills/romiluz13/cc10x/memory-and-handoff"><img src="https://agentmods.dev/badge/skills/romiluz13/cc10x/memory-and-handoff/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/romiluz13/cc10x/memory-and-handoff"><img src="https://agentmods.dev/badge/skills/romiluz13/cc10x/memory-and-handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00070 | $0.02522 |
| Opus 5.5 | $0.00028 | $0.01009 |
| Sonnet 5.5 | $0.00014 | $0.00504 |
| Haiku 4.5 | $0.00007 | $0.00252 |
Grade A, and why
memory-and-handoff 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 2d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory & Handoff
Reference Files
Read only what's needed:
references/memory-model-and-ownership.md— memory surfaces, ownership, promotion, workflow markers; load when deciding which surface holds a piece of state or who may write itreferences/memory-operations.md— permission-free operations, router-only persistence, edit patterns; load when actually reading or writing.cc10x/filesreferences/memory-file-contracts.md— required headings, stable anchors, templates, auto-heal rules; load when creating a memory file or healing a malformed onereferences/context-budget-and-checkpointing.md— context-budget rules, warning signs, checkpoint triggers; load when context is getting heavy or before a compaction/checkpoint decision
Mode: SESSION MEMORY
Memory is an index, not a transcript. Distill decisions, learnings, references, and verification evidence into durable, reusable notes.
Memory Surfaces
| File | Holds |
|---|---|
.cc10x/activeContext.md |
current focus, recent changes, decisions, learnings, references, blockers |
.cc10x/patterns.md |
reusable project standards, gotchas, conventions, skill hints |
.cc10x/progress.md |
current workflow, tasks snapshot, completed items, verification evidence |
.cc10x/workflows/{wf}.json + .events.jsonl |
durable orchestration truth (machine-owned, verbatim) |
.cc10x/qa/ |
QA route artifacts: {workflow_uuid}/feature-map.md, test-plan.md, env-plan.md, report.md, and per-environment env/{env_key}/setup.md (router- and QA-agent-owned) |
.cc10x/state/ |
hook-mode report markers (hook-mode-reported-*), so an invalid hook-mode.json is logged once per file state |
docs/plans/*, docs/research/* |
detailed artifacts; memory points to them |
Ownership
- Router loads and auto-heals memory files before routing or resume
- WRITE agents read memory but do NOT edit
.cc10x/*.md(sole carve-out: bug-investigator's[DEBUG-N]lines) - WRITE agents emit structured
MEMORY_NOTESin their Router Contract - READ-ONLY agents emit
### Memory Notes (For Workflow-Final Persistence) - Router-owned memory-finalize task is the only final writer of memory markdown files
- Router-owned markers (
[DEBUG-RESET: wf:{...}],[cc10x-internal] memory_task_id) are read and respected; agents do not invent replacements
What ships with it
4 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.
- 2d ago Changed 38ecc1491cd2
- 14d ago Changed · +4 lines 116a4cf95a02
- 1mo ago First seen · 176 lines · 70 tokens per session scan A 50e3bdddcb66
memory-and-handoff is a skill published in the GitHub repository romiluz13/cc10x (165 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 2,522 once invoked, about $0.0003 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
meta-harness
Run one iteration of memory system evolution. Called by metaharness.py or interactively via /meta-harness.
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
create-request
Create, update, or scan per-task request tickets for progress tracking. These are date-prefixed non-lifecycle docs under requests/, NOT feature-level requirements (use /req-analyze for those). Use when: tracking task progress, updating completion status, scanning incomplete requests, checking request status dashboard.…
gh-stack
Native stacked pull requests through the github/gh-stack extension. Detects the extension, installs it only after the user approves, resolves the branch chain, and executes gh stack link / gh stack push / gh stack submit --auto under a per-use AskUserQuestion gate. Use when: opening or refreshing a native stack of…
smart-rebase
Smart partial rebase for squash-merge repositories. Auto-detect which commits to keep/drop when base branch was squash-merged into target. Use when: user says 'rebase', 'partial rebase', 'base already merged', 'smart rebase', or /smart-rebase. Not for: simple git rebase (the developer runs it — no skill executes…
remind
A correction helper that checks which project rules or required steps were missed and loads the relevant guidance.