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 skills/helixdevelopment/code/session-syncnpx skills add HelixDevelopment/code --skill session-syncgit clone --depth 1 https://github.com/HelixDevelopment/codeWhat 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.00022 | $0.00479 |
| Opus 5 | $0.00011 | $0.00239 |
| Sonnet 5 | $0.00004 | $0.00096 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
session-sync 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.
What it actually says
You are helping a HelixCode user sync session state with the same project on another machine.
Session sync moves the project's agent-side state — memories, session transcripts, settings, agent definitions and handoff documents — between a remote host and this one. It supports pull (remote to local), push (local to remote) and bidirectional sync.
Before running anything, establish these facts rather than assuming them:
-
DIRECTION. Pull, push, or bidirectional. Never guess: pushing when the user meant pull can overwrite newer local state.
-
THE REMOTE. Which host, which user, and the path to the SAME project there. Sync is defined between two checkouts of one project; it is not a general file copy.
-
WHAT IS IN SCOPE. Session transcripts and memories are the point. Anything holding credentials is not: never sync secrets, tokens, key material or
.envfiles between machines as part of this operation. -
CONFLICTS ARE SURFACED, NOT SILENTLY MERGED. When both sides changed, report the divergence and let the user decide. Silently picking a winner destroys whichever side lost.
-
THE OPERATION MUST BE REVERSIBLE. Confirm a backup or a dry run before any step that overwrites existing local state, and prefer showing what WOULD change first.
Report afterwards what actually transferred — which files, in which direction — rather than reporting success generically. If the remote was unreachable, say so; an unreachable remote is not a completed sync.
The sync implementation and its full contract live at
constitution/skills/session-sync/ alongside the executable helper.
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 First seen · 44 lines · 22 tokens per session scan A a30859b1be8f
session-sync is a skill published in the GitHub repository HelixDevelopment/code (2 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session and 479 once invoked, about $0.0001 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 skills, from other repositories
reskin
Author a NEW skin for the reskinnable-demo app. A skin is a self-contained domain plugin under src/skins/ / that implements the frozen Skin contract (src/shell/skin-contract.ts) to swap the app's entire experience — brand, theme, layout, pages, tools, data, and agent — as a live sales demo. Use when the user says "add…
copilotkit-channels
Use for the CODE half of a managed Intelligence Channel with Slack or Microsoft Teams: customising the Channel a CLI-scaffolded project already ships, or — for a project the CLI did not generate — writing the Channel declaration, the long-running host, and the awaited activation call. Teams provider setup is in scope…
copilotkit-setup
Use when adding CopilotKit to an existing project or bootstrapping a new CopilotKit project from scratch. Covers framework detection, package installation, runtime wiring (managed Intelligence or self-hosted SSE), provider setup, and first working chat integration.
setup-slack-channel
Use for the PROVIDER half of getting a locally running CopilotKit Channels agent to answer in Slack, when no Slack app exists yet — setting up a Channels bot in Slack for the first time, creating the Slack app and its tokens, attaching it to a managed Intelligence Channel, or when a Channel reports setuprequired, sits…
a2ui-renderer
Render A2UI (Agent-to-UI declarative surfaces) in CopilotKit v2. Enable the runtime via CopilotRuntime({ a2ui: {...} }), then enable the provider via . Auto-activates via /info — do NOT manually pass renderActivityMessages. createA2UIMessageRenderer ships from @copilotkit/react-core/v2; low-level primitives…
runtime
@copilotkit/runtime — mount a fetch-native CopilotRuntime on any JS server, wire middleware, pick an AgentRunner, instantiate BuiltInAgent (Factory Mode with TanStack AI is the preferred default) or plug in any of 12 external agent frameworks (Mastra, LangGraph, CrewAI Crews/Flows, PydanticAI, ADK, LlamaIndex, Agno…