What is design-department?

An interactive process for creating a new top-level department with a charter, responsibilities, and optional leadership recommendation.

Use it when establishing a department such as data engineering or customer success. For a department inside another department, use a sub-department process instead.

It helps define a department’s place in the organization before creating its folder and ongoing work structure.

How Koroqe/OPOS configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Koroqe/OPOS. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Koroqe/OPOS/main/.claude/skills/design-department/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/Koroqe/OPOS

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/koroqe/opos/design-department/github.svg)](https://agentmods.dev/skills/koroqe/opos/design-department)

Your own site

<a href="https://agentmods.dev/skills/koroqe/opos/design-department"><img src="https://agentmods.dev/badge/skills/koroqe/opos/design-department/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/koroqe/opos/design-department"><img src="https://agentmods.dev/badge/skills/koroqe/opos/design-department.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 5,023 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00061	$0.05023
Opus 5	$0.00030	$0.02511
Sonnet 5	$0.00012	$0.01005
Haiku 4.5	$0.00006	$0.00502

Measured 6d ago against content hash e594d3587e31, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade B, and why

design-department 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 6d 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.

Enumerates other installed skillsmediumAgent snooping

Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.

12. **Write design-department's own history entry.** Append to `.claude/skills/design-department/history/YYYY-MM-DD-<short-run-id>.md` per the `.claude/CLAUDE.md` schema (including the optional `time: HH:MM` from v0.3.1)

.claude/skills/design-department/SKILL.md · 155 lines

How it starts

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

design-department

When to use

Invoke when a new top-level department needs to exist. Two entry points:

Fresh dept description — the user says "we need a department for X" (e.g., "customer-success", "data engineering", "product research").
Formalize a backlog item — the user points at a BACKLOG-ITEM.md whose intended_target is a dept.

The skill is INTERACTIVE: it produces a proposal, iterates with the user, and only writes the dept charter on explicit user approval. The human is the approval gate. This is the third member of the design-* family — after design-process (v0.1.0) and design-agent (v0.4.0). All three are owned by ops-manager; together they close the org-chart-expansion loop end-to-end (skills, agents, depts).

Top-level only. This skill handles top-level depts. Sub-depts are first-class as of v0.8.0 — use /design-subdept --parent <name> for sub-depts (e.g., compliance under legal, data under rnd). Two patterns now exist for sub-organization: /design-agent for a sub-role agent under the parent's agents folder (the v0.5.1 eng-lead-under-rnd pattern); /design-subdept for a sub-dept with its own charter/data/backlog/skills scope (the v0.8.0 capability). When in doubt, start with /design-agent (lighter weight); promote to a sub-dept later via /design-subdept if scope warrants.

Inputs

dept_description — free-text description of what the new dept owns, its function, authority, interface, and (optionally) a suggested name. Required if no backlog_item_path.
backlog_item_path — OPTIONAL. Path to a BACKLOG-ITEM.md whose intended_target is a dept. When supplied, the item's frontmatter seeds the proposal; the item is flipped to state: designed with a designed_as: departments/<name>/ field at step 11.
design_lead_agent — OPTIONAL bool (default: ASK the user during step 5). When yes, the skill captures the proposed lead-agent name + a brief role description and emits a /design-agent recommendation at step 11 (NOT auto-invoked — see step 5 rationale). When no, the charter ships with <dept-name>-lead as the placeholder Roles entry; the user designs the lead later.

Read the full file on GitHub · 155 lines

Files

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.

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.

6d ago Changed e594d3587e31
10d ago First seen · 155 lines · 61 tokens per session scan B 36a241ca541b

Subscribe to this mod's changes

design-department is a skill published in the GitHub repository Koroqe/OPOS (2 stars, last pushed 9d ago), licensed MIT. It adds 61 tokens to every session and 5,023 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning dept-design framework meta

super-evolve

Ultimate self-evolution skill. Merges evolve + self-improve into one comprehensive meta-skill with external research, area focus, dry-run mode, and expanded memory mining.

OZmasterAI/Torus-Framework · 35 tokens

pr-to-video

Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR…

heygen-com/hyperframes · 104 tokens

general-video

Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated…

heygen-com/hyperframes · 92 tokens

OPOS: Skill for Claude Code