Borrowing it
Nothing to install: this file belongs to suisya-systems/claude-org-ja. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/suisya-systems/claude-org-ja/main/.claude/skills/org-start/SKILL.mdgit clone --depth 1 https://github.com/suisya-systems/claude-org-jaWrote 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/suisya-systems/claude-org-ja/org-start)<a href="https://agentmods.dev/skills/suisya-systems/claude-org-ja/org-start"><img src="https://agentmods.dev/badge/skills/suisya-systems/claude-org-ja/org-start/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/suisya-systems/claude-org-ja/org-start"><img src="https://agentmods.dev/badge/skills/suisya-systems/claude-org-ja/org-start.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 177 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- medium Rogue Agent · line 261 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Agent Snooping · line 394 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 437 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00071 | $0.21052 |
| Opus 5.5 | $0.00028 | $0.08421 |
| Sonnet 5.5 | $0.00014 | $0.04210 |
| Haiku 4.5 | $0.00007 | $0.02105 |
Grade A, and why
org-start scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> **sandbox 注記（false negative 回避）**: Claude Code の Bash sandbox はネットワーク / プロセス namespace が隔離されているため、本 Block の常駐起動・疎通確認を sandbox 内で行うと誤判定する。ホスト側で server が正常に listen していても、sandbox 内では `curl` が `000` を返し、`ss` に port が見えず、`p How it starts
The opening of the file, as written. The whole thing — 515 lines — stays where its author put it; the contents beside it link to each section on GitHub.
org-start: 組織の起動
ClaudeCode起動後に最初に実行するスキル。前回の状態復元とディスパッチャー起動を行う。
キュレーターは起動しない: worker クローズ時の閾値チェックでディスパッチャーがオンデマンド起動する （
.dispatcher/references/pane-close.mdStep 5）。 org-start では curator の identity をStateWriter.CLEARで明示クリアする（Block D-5）。 curator 不在（null）が正常系である。設計メモ・経緯は.claude/skills/org-start/references/rationale.md。
前提: この Claude は
renga --layout opsで起動された窓口ペイン内で動作している。RENGA_SOCKET/RENGA_PANE_ID環境変数が継承されているので、mcp__renga-peers__*MCP ツール 14 種（spawn_pane/spawn_claude_pane/close_pane/focus_pane/list_panes/new_tab/send_message/list_peers/set_summary/check_messages/inspect_pane/poll_events/send_keys/set_pane_identity）でペイン操作・ピア通信・画面スクレイプ・lifecycle event 購読・raw キー入力まですべてカバーできる（renga 0.18.0+ で導入された構造。現行 org の renga transport サポート下限は 2.0.0）。 ただしこの 14 種はタブ scope が一様ではない（pane 制御 / Group B / messaging / 例外）。分類の正本はdocs/contracts/backend-interface-contract.mdT-§cap / T-§4.2、要約は.claude/skills/org-start/references/rationale.md。state DB 前提:
.state/state.dbが唯一の SoT。 read 経路は DB のみ、構造化セクション (Status / Dispatcher / Curator / Worker Directory Registry / Active Work Items / Resume Instructions) の write 経路はStateWriter.transaction()経由（post-commit hook が.state/org-state.mdを DB から自動再生成、markdown 直接編集禁止 — drift_check が検出する）。free-form ノート（学び / Pending Lead 等） はnotes/配下に保存する。 DB が無い場合はpython3 -m tools.state_db.importer --db .state/state.db --root . --rebuild --no-strictで構築する。
輸送層（transport）両系 — 既定
renga/ opt-inbroker: 本スキルのmcp__renga-peers__*呼び出しは 既定renga（ORG_TRANSPORT無設定）で書いてあり、そのまま従えばよい（既定挙動は不変）。ORG_TRANSPORT=broker（opt-in・切戻し可）では MCP サーバー名がorg-brokerになり、ツールの 完全修飾名がmcp__renga-peers__*→mcp__org-broker__*に機械置換される（引数形・セマンティクスは同一なので手順の論理は変わらない）。輸送依存で手順が変わる点だけ broker 併記する:
- 受信モデル（push 一次 =
claude/channel/ pull フォールバック）: renga は dispatcher / worker のメッセージが<channel source="renga-peers" …>として in-band で push される。broker は push 一次に再設計されている（runtime push-first 0.1.24+、transport-labdocs/design/broker-native-roles.md§9）: 各ペイン同居の channel sidecar（server:org-broker-channel）が broker キューを ~1 秒間隔で claim→push し、notifications/claude/channelで本文を idle セッションへ注入する（renga の in-band push と同じ「受けたら即応答」契機）。pull はフォールバック層: sidecar 不在 / unhealthy（heartbeat timeout でdelivery_mode=PULL）/ channel 非対応ペイン / claude.ai login 不在時は、各役割が自身の cadence で能動的にcheck_messages（broker ではmcp__org-broker__check_messages）する（§9.6 読み替え表の役割別 cadence。ナッジが出れば契機になりうるが idle を起こさないため能動 poll が受信の正路。既存の「ナッジを見たらcheck_messages」prose は撤回せずこの fallback cadence として読む。ツール名以外の手順は同型）。契約面は Surface 8 で push 一次が ratified 済み（2026-06-15、S3。broker pull-only を supersede し pull は fallback として retain・renga 不変）。- spawn 儀式（folder-trust 承認 + dev-channel sidecar 承認の再導入）: renga の
spawn_claude_paneは--dangerously-load-development-channels server:renga-peersを注入し「Load development channel?」を画面判定で承認する（Block D-1）。broker は--mcp-config <broker>を注入し承認プロンプトが Claude Code の folder-trust プロンプトに変わる（画面判定で機械承認）のに加えて、push 一次のため channel sidecar を--dangerously-load-development-channels server:org-broker-channelで load し dev-channel 承認プロンプト（spawn-flow 3-3b）を画面判定で 再導入機械承認する（ratified §5/§8.5 の folder-trust フローへの加算であり置換ではない。設計は broker-native-roles.md §9.5）。画面判定 =inspect_pane→claude-org-runtime dispatcher spawn-prompt-stepが返した 1 手だけをsend_keysする反復（runtime 0.1.43+）。盲目 Enter は禁止（folder-trust の初期カーソルは「No, exit」で、Enter 一発は起動したセッションを終了させる）。- エラー分岐（broker 追加コード）: renga コード（
[split_refused]/[pane_not_found]/[cwd_invalid]等）に加え broker は[token_invalid]/[session_invalid]/[tool_not_authorized]/[no_backend]（= adapter_unavailable）/[nudge_failed]/[peer_not_found]/[name_taken]を返しうる（未知コードは default-branch で escalate）。一覧は.claude/skills/org-delegate/references/renga-error-codes.mdの broker 節を参照。
new_tab/focus_paneは broker surface に無い（意図的除外。本フローは元々使わない）。契約面の正本はdocs/contracts/backend-interface-contract.mdSurface 8（broker auth & delivery、ratified 2026-06-14。push 一次への additive 改訂 S3 が ratified 済み（2026-06-15、「Ratified amendment」節）・既存 ratified 本文不変更）、設計 SoT は transport-labdocs/design/broker-native-roles.md§9（push 一次再設計）/docs/design/ja-migration-plan.md§5.2(ii)・§8。broker 実走（dogfood）は Epic #6 Issue G スコープで本スキルの既定経路ではない。（既定の二フレーム注記（Refs #604）: ここでの「既定
renga」は運用既定（broker 実走 dogfood が Epic #6 Issue G まで未活性）の意。別にコード既定としてtools/transport.py: DEFAULT_TRANSPORTが runtime 0.1.28 (Epic #586) でbrokerにフリップ済みで、ja 生成器・transport.resolve()はこのコードフレームで render するため生成面は「既定broker」と表示する — 両フレームは指す対象（運用経路 vs コード定数）が異なり矛盾しない。総説は rootCLAUDE.md「輸送層（transport）両系」節。）
What ships with it
1 file 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.
- 4d ago Changed · +6 lines f9dcc84ec035
- 12d ago Changed · -35 lines · -34 tokens per session ca095cb46de4
- 1mo ago Changed · +7 lines 9a8189cfe90a
- 2mo ago First seen · 537 lines · 105 tokens per session scan A d0bd881a3d3e
org-start is a skill published in the GitHub repository suisya-systems/claude-org-ja (5 stars, last pushed 5d ago), licensed MIT. It adds 71 tokens to every session and 21,052 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
board
Read and write the workspace BOARD.md (shared task board for agents + Val). Wraps bin/board, a small Python CLI that preserves the markdown schema and appends to the activity log automatically. Use this whenever an agent proposes, claims, or finishes work that should be visible to the rest of the roster.
ai-agent-job-marketplace
The job marketplace where bots hire bots. Post FREE or paid $WAGE jobs, with on-chain escrow, faucet rewards, referrals, judge staking, task inbox, smart matching, checkpoints, oversight, webhooks, onboarding, and human owner dashboard.
agent-freelance-bounty-marketplace
Earn USDC completing bounties, post jobs, join multi-agent raids, build reputation, rank up. AI agent freelance marketplace with x402 escrow on Solana. Free SOL airdrop on signup. Guilds, ranks, vouching, disputes, Castle Town, leaderboard.
agent-job-marketplace-with-bidding
Agent-to-agent marketplace MVP. Agents post jobs, bid, contract, submit deliverables, and leave reviews. Payments are off-platform (crypto) in v1.
advise-engineering-technical-leadership
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO…
agent-team-collaboration-marketplace
The marketplace for AI agents to form teams and collaborate on projects. Find teammates, join teams, build together.