메뉴
Use when configuring or troubleshooting secrets, sops injection, and auth boundaries across daemon, worker, and Telegram
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when deploying pigeon code changes across all machines after merging to main
Use when you need to understand worker architecture, endpoint flow, and command routing behavior before making changes
Use when you need to understand daemon route flow, storage model, worker connectivity, and command injection architecture before making changes
Use when you need to understand the OpenCode plugin event lifecycle, session state transitions, and daemon API contracts
Use when developing or refactoring OpenCode plugin handlers, tests, and daemon integration payloads
Use when you need to understand the swarm IPC subsystem — tables, routes, the per-target arbiter, the session→directory registry, and the wire envelope — before changing it
| name | secrets-and-auth |
| description | Use when configuring or troubleshooting secrets, sops injection, and auth boundaries across daemon, worker, and Telegram |
Use this for secret setup, auth failures, or token rotation.
/run/secrets/ at boot on Linux.CCR_API_KEYTELEGRAM_BOT_TOKENTELEGRAM_WEBHOOK_SECRETTELEGRAM_CHAT_ID / TELEGRAM_GROUP_IDCLOUDFLARE_API_TOKENCCR_API_KEY (poll, ack, sessions, notifications, media)Authorization: Bearer CCR_API_KEY headerX-Telegram-Bot-Api-Secret-TokenALLOWED_USER_IDS (optional): comma-separated Telegram user IDs. If set, only these users can interact with the bot within allowed chats. If unset, all users in allowed chats are permitted.http://127.0.0.1:4096): no auth -- localhost-only, single-user machine; password was intentionally removed as marginal security valuecat /run/secrets/ccr_api_key | head -c5 && echo "...ok"
curl -s -o /tmp/sessions.json -w "%{http_code}" -H "Authorization: Bearer $(cat /run/secrets/ccr_api_key)" "https://ccr-router.jonathan-mohrbacher.workers.dev/sessions"
Expected:
200