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 Arch1eSUN/Arcgentic --skill cross-session-handoffgit clone --depth 1 https://github.com/Arch1eSUN/ArcgenticWrote 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/arch1esun/arcgentic/cross-session-handoff)<a href="https://agentmods.dev/skills/arch1esun/arcgentic/cross-session-handoff"><img src="https://agentmods.dev/badge/skills/arch1esun/arcgentic/cross-session-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/arch1esun/arcgentic/cross-session-handoff"><img src="https://agentmods.dev/badge/skills/arch1esun/arcgentic/cross-session-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.00031 | $0.00227 |
| Opus 5 | $0.00015 | $0.00113 |
| Sonnet 5 | $0.00006 | $0.00045 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
cross-session-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 10d 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.
What it actually says
cross-session-handoff
Manages .arcgentic/state.yaml as the shared state medium across multiple AI
sessions.
Commands
arcgentic cross-session-handoff read
arcgentic cross-session-handoff write --session-id dev-session --updates '{"current_phase":"dev"}'
arcgentic cross-session-handoff snapshot --session-id audit-session
arcgentic cross-session-handoff acquire-lock --session-id dev-session --ttl 600
arcgentic cross-session-handoff release-lock --session-id dev-session
Rules
- Reads do not acquire a lock.
- Writes acquire a TTL lock, write through a temp file, then rename atomically.
- Snapshots go to
.arcgentic/state-history/. - A session must not overwrite another non-expired lock.
See also
toolkit/src/arcgentic/skills_impl/cross_session_handoff.py
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.
- 10d ago First seen · 32 lines · 31 tokens per session scan A 80a17873a6fe
cross-session-handoff is a skill published in the GitHub repository Arch1eSUN/Arcgentic (287 stars, last pushed 28d ago), licensed MIT. It adds 31 tokens to every session and 227 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-30.
Other skills, from other repositories
evolving-status
View Self-Evolving Loop session status, history, and memory metrics.
debt-ops-init
Write or refresh a "Tech debt operations" section in the project's AGENTS.md so the team shares one source of truth for debt-ops disciplines. Run ONLY when the user explicitly asks to set up, install, or initialize debt-ops disciplines — never auto-invoke. Idempotent; only the managed section changes, other sections…
performance-audit
Full-stack performance health check across 12 dimensions. Rendering, bundles, assets, API/network, algorithms, memory, database, caching, Web Vitals, backend runtime, concurrency, and framework-specific pathologies. Evidence-based Impact Models with confidence tiers and a prioritized optimization roadmap. Switches…
debt-ops-add
Register a deferred decision in the tech-debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you…
debt-ops-metrics
Print a debt-ops health summary from the metrics log, covering registration rate, feedback action rate, ADR creation, and AI-authored share. Use when the user asks for "debt-ops metrics", "debt health", "registry stats", or a tech-debt health summary. Read-only, never writes the log.
ccc-handoff
Proactive context reset — write a dense handoff file and tell the user to start a NEW chat now. Context degrades quality as it fills; fix is frequent handoffs, not deeper compaction.