attach

Bind an activated agent to its channel surface with correct mode and cursor state.

8|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/usurobor/cnos --skill attach-usurobor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: attach
Source: https://github.com/usurobor/cnos/tree/main/src/packages/cnos.core/skills/agent/attach
Command: npx skills add https://github.com/usurobor/cnos --skill attach-usurobor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill binds an activated agent to a channel surface, ensuring correct mode detection (home, foreign-activation, or ephemeral) and proper cursor synchronization to prevent channel drift.

Core Features & Use Cases

  • Detect environment: home, foreign-activation, or ephemeral, and identify the appropriate channel surfaces.
  • Choose and execute the correct attach or sync procedure based on mode and attachment state.
  • Maintain channel integrity by frontmatter-cursor tracking and avoiding speculative entries.

Quick Start

Activate the agent and then attach to bind the identity to the hub channel.

Frequently Asked Questions about attach

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bind an activated agent to a channel surface after workflow activation?

To bind an activated agent to a channel surface, you use a post-activation workflow procedure that detects the environment mode and synchronizes the cursor state. This ensures the agent identity is reliably attached to the hub channel without speculative entries.

How does cursor synchronization prevent channel drift when attaching agents to a hub?

Cursor synchronization prevents channel drift by reading the hub state and writing per frontmatter cursor metadata. This tracking mechanism ensures the agent remains correctly bound to its channel surface across different operational modes.

What is the difference between home, foreign-activation, and ephemeral modes for agent channel attachment?

Home, foreign-activation, and ephemeral modes represent different runtime environments for an activated agent. The attachment procedure detects the current mode to identify the correct channel surfaces and execute the appropriate sync procedure for that specific context.

Do I need prior agent activation to attach it to a hub channel?

Yes, prior agent activation is required to attach it to a hub channel. You must also have access to agent and channel surfaces, as the attachment process enforces a no-guess rule and operator deferment to maintain channel integrity.

Why does my agent channel attachment fail when hub state is not readable?

Agent channel attachment fails when hub state is unreadable because the procedure relies on reading hub state to detect the correct mode and write per frontmatter cursor metadata. The no-guess rule prevents speculative entries when state data is missing.