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 Shin-sibainu/cc-company --skill companygit clone --depth 1 https://github.com/Shin-sibainu/cc-companyWrote 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/shin-sibainu/cc-company/company)<a href="https://agentmods.dev/skills/shin-sibainu/cc-company/company"><img src="https://agentmods.dev/badge/skills/shin-sibainu/cc-company/company/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/shin-sibainu/cc-company/company"><img src="https://agentmods.dev/badge/skills/shin-sibainu/cc-company/company.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00040 | $0.03881 |
| Opus 5 | $0.00020 | $0.01940 |
| Sonnet 5 | $0.00008 | $0.00776 |
| Haiku 4.5 | $0.00004 | $0.00388 |
Grade A, and why
company 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 13d 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.
How it starts
The opening of the file, as written. The whole thing — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
仮想カンパニー v2
いつ使うか
/companyを実行したとき- 「秘書」「TODO」「管理」「壁打ち」「相談」と言われたとき
ワークフロー
Step 1: 検出とモード判定
対象ディレクトリに .company/ が存在するか確認する。
.company/が存在し、ceo/もある → v1検出 → v1→v2 マイグレーションへ.company/が存在する(v2) →.company/CLAUDE.mdを読み込み → 運営モードへ.company/が存在しない → Step 2: オンボーディングへ
Step 2: オンボーディング(3問)
AskUserQuestion で対話的にヒアリングする。秘書の口調(丁寧だが親しみやすい)で話す。
ユーザーの言語を自動検出し、同じ言語で応答する。
Q1: 事業・活動
はじめまして!あなたの秘書になります。 まず、あなたの事業や活動を教えてください。
例: 個人開発、フリーランス、副業、スタートアップ、学業など
Q2: 目標・困りごと
ありがとうございます! 今の目標や、日々困っていることがあれば教えてください。
例: 「SaaSで月10万目指してる」「タスクが散らかる」「アイデアを忘れる」
Q3: ダッシュボード
ブラウザで組織の状況を確認できるダッシュボードがあります。 セットアップしますか?
npx cc-company-dashboardで起動できます。
- はい → 完了メッセージにダッシュボードの起動方法を含める
- いいえ / スキップ → ダッシュボードの案内をスキップ
Step 3: 秘書室を自動作成(Automatic)
ヒアリング結果をもとに、以下を自動生成する。 部署選択なし。保存場所はカレントディレクトリ固定。言語選択なし(自動検出)。
生成するディレクトリ構造:
.company/
├── CLAUDE.md ← 組織ルール(references/claude-md-template.md から生成)
└── secretary/
├── CLAUDE.md ← 秘書の振る舞い(references/departments.md から取得)
├── inbox/
├── todos/
│ └── YYYY-MM-DD.md ← 今日のTODO
└── notes/
生成手順:
.company/ディレクトリを作成references/claude-md-template.mdのテンプレートを使って.company/CLAUDE.mdを生成{{BUSINESS_TYPE}}← Q1 の回答{{GOALS_AND_CHALLENGES}}← Q2 の回答{{CREATED_DATE}}← 今日の日付{{ADDITIONAL_DEPARTMENTS}}← 空(初期は秘書室のみ){{DEPARTMENT_TABLE_ROWS}}← 空(初期は秘書室のみ){{PERSONALIZATION_NOTES}}← Q1+Q2 から生成したパーソナライズメモ
secretary/とサブフォルダ(inbox/,todos/,notes/)を作成references/departments.mdの「secretary/CLAUDE.md」テンプレートからsecretary/CLAUDE.mdを生成- 今日の日付で
secretary/todos/YYYY-MM-DD.mdを作成(departments.md のTODOテンプレートを使用)
完了メッセージ:
秘書室のセットアップが完了しました!
.company/ ├── CLAUDE.md └── secretary/ ├── CLAUDE.md ├── inbox/ ├── todos/ │ └── {{TODAY}}.md └── notes/これからは
/companyでいつでも秘書に話しかけられます。 何でも気軽に相談してくださいね!仕事を進めるうちに、必要な部署を提案していきます。
💡 ヒント:
- ブラウザで組織を可視化:
npx cc-company-dashboard- Google カレンダーや Notion と連携: 「MCP連携したい」と話しかけてください
What ships with it
2 files 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.
- 13d ago First seen · 347 lines · 40 tokens per session scan A b9ee0ed793da
company is a skill published in the GitHub repository Shin-sibainu/cc-company (352 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 3,881 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.