orgkit-init

A repository-onboarding command that examines what each folder contains, proposes an organizational structure, and creates orgkit role and memory files after you review the proposal.

In plain words
What is it for?
Use it to organize an unfamiliar repository into roles, create `.org/roles.json`, and start orgkit's memory system.
Why use it?
It removes the need to map a code repository by hand or rely on folder names alone. It also checks whether the repository has already been onboarded.

Command

Install

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.

agentmods
npx agentmods add commands/hdk10/orgkit/orgkit-init
Clone the repo
git clone --depth 1 https://github.com/hdk10/orgkit
Per session 51 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,334 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00051 $0.03334
Opus 5 $0.00026 $0.01667
Sonnet 5 $0.00010 $0.00667
Haiku 4.5 $0.00005 $0.00333

Measured yesterday against content hash 28166d45d601, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

orgkit-init scanned grade B 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 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

`~/.claude/settings.json` (creating it if missing). Watch the output: it may
commands/orgkit-init.md · 246 lines

How it starts

The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the intelligent onboarding agent for orgkit. Your job is NOT to run a Python heuristic and blindly accept its output. Your job is to read the repo yourself, understand what each folder actually IS, and propose a sensible org structure backed by real rationale.

The Python tool handles mechanics. You handle judgment.


Step 1 — Locate the repo and check onboarding state

The user's repo root is ${CLAUDE_PROJECT_DIR} (fall back to $PWD).

Check whether ${CLAUDE_PROJECT_DIR}/.org/roles.json already exists.

  • If it exists: tell the user the repo is already an orgkit repo and suggest /org-status instead. Use AskUserQuestion to ask whether they want to re-run onboarding (re-design roles from scratch) before continuing.

Step 2 — Extract deterministic folder signals

Run the scanner to get a compact, token-bounded signal payload.

Prefer the installed engine if it exists; fall back to the plugin copy:

# Use whichever exists:
#   .org/scan.py  — installed engine (preferred)
#   ${CLAUDE_PLUGIN_ROOT}/orgkit/scan.py  — plugin copy (pre-install fallback)
if [ -f "${CLAUDE_PROJECT_DIR:-$PWD}/.org/scan.py" ]; then
  python3 "${CLAUDE_PROJECT_DIR:-$PWD}/.org/scan.py" --target "${CLAUDE_PROJECT_DIR:-$PWD}" --json
else
  python3 "${CLAUDE_PLUGIN_ROOT}/orgkit/scan.py" --target "${CLAUDE_PROJECT_DIR:-$PWD}" --json
fi

Parse the JSON. You now have, for every top-level folder:

  • name — the folder name (may be cryptic: proj-final/, v2/, temp2/)
  • file_count — total files inside
  • top_exts — top 5 file extensions with counts
  • kind — coarse classification: python / node / web / data / docs / infra / mixed
  • telltale — telltale files present (package.json, pyproject.toml, Dockerfile, etc.)
  • excerpt — up to ~300 chars from the README or entry point

Step 3 — YOU reason over the signals (the intelligent step)

Do not fall back to keyword matching. Read the signals. For any folder where:

  • the kind is mixed or docs, or
  • the name is cryptic / ambiguous (e.g. v2/, experiments/, proj-final/, temp-client/), or
  • the excerpt is empty or unhelpful

Read the full file on GitHub · 246 lines

Changes

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.

  1. yesterday First seen · 246 lines · 0 tokens per session scan B 28166d45d601

Subscribe to this mod's changes

orgkit-init is a command published in the GitHub repository hdk10/orgkit (2 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 3,334 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.