OPOS: Skill for Claude Code

.claude/skills/design-subdept/SKILL.md

design-subdept is a skill for Claude Code from Koroqe/OPOS. It costs 76 tokens per session (5,824 once invoked), scanned A, original, MIT.

An organizational design process for splitting an existing department into a smaller sub-department with its own scope, backlog, data, and guidance.

In plain words
What is it for?
Use it when creating a sub-department such as compliance under legal or data under research and development, with human approval before the charter is written.
Why use it?
It gives a proposed sub-department a defined role and reporting path instead of adding an unclear folder or informal responsibility.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

This is Koroqe/OPOS's own configuration. It tells Claude Code how to work on OPOS itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything OPOS configures →

View source ↗ Koroqe/OPOS
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-subdept/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.

agentmods badge for design-subdept

README.md
[![agentmods](https://agentmods.dev/badge/skills/koroqe/opos/design-subdept/github.svg)](https://agentmods.dev/skills/koroqe/opos/design-subdept)
Your own site
<a href="https://agentmods.dev/skills/koroqe/opos/design-subdept"><img src="https://agentmods.dev/badge/skills/koroqe/opos/design-subdept/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.

agentmods 80×15 button for design-subdept

Your own site · 80×15
<a href="https://agentmods.dev/skills/koroqe/opos/design-subdept"><img src="https://agentmods.dev/badge/skills/koroqe/opos/design-subdept.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,824 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00076 $0.05824
Opus 5 $0.00038 $0.02912
Sonnet 5 $0.00015 $0.01165
Haiku 4.5 $0.00008 $0.00582

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

Security

Grade A, and why

design-subdept 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 5d 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.

.claude/skills/design-subdept/SKILL.md · 188 lines

How it starts

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

design-subdept

When to use

Invoke when an existing top-level department needs to be sub-divided into a sub-dept with its own organizational scope (own backlog, own data, own skills folder, cascade-inherited charter). Three entry points:

  1. Fresh sub-dept description — the user says "we need a compliance sub-dept under legal" or "data should be its own thing under rnd."
  2. Formalize a backlog item — the user points at a BACKLOG-ITEM.md whose intended_target is a sub-dept.
  3. Escalation from design-department — when the user asks for a top-level dept that's really a sub-organization of an existing one, design-department directs them here.

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

Depth-2 only (sub-sub-depts NOT supported). v0.8.0 ships top-level → sub-dept (depth 1 → depth 2). Depth-3 (A under B under C) is intentionally not supported — see step 4 for recovery paths.

Inputs

  • parent_dept — required; the existing top-level dept slug (e.g., legal, rnd). Must match an existing folder under departments/.
  • subdept_description — required (unless backlog_item_path is supplied); free-text description of what the sub-dept owns + optionally a suggested name.
  • backlog_item_path — OPTIONAL. Path to a BACKLOG-ITEM.md whose intended_target is a sub-dept. When supplied, the item's frontmatter seeds the proposal; the item is flipped to state: designed with a designed_as: departments/<parent>/<sub>/ field at step 11.
  • design_lead_agent — OPTIONAL bool (default: ASK the user during step 5). When yes, the skill emits a /design-agent recommendation at step 11 for the next turn. When no, the charter ships with <sub-name>-lead as the placeholder Roles entry; the user designs the lead later.

Read the full file on GitHub · 188 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.

  1. 5d ago Changed 519235987aef
  2. 9d ago First seen · 188 lines · 76 tokens per session scan A 4d356d60174b

Subscribe to this mod's changes

design-subdept is a skill published in the GitHub repository Koroqe/OPOS (2 stars, last pushed 7d ago), licensed MIT. It adds 76 tokens to every session and 5,824 once invoked, about $0.0004 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-31.

Related

Other skills, from other repositories

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

torchforge-rl-training

Provides guidance for PyTorch-native agentic RL using torchforge, Meta's library separating infra from algorithms. Use when you want clean RL abstractions, easy algorithm experimentation, or scalable training with Monarch and TorchTitan.

davila7/claude-code-templates · 49 tokens

horse-integration-tests

Guide for writing automated integration tests for Horse endpoints using DUnit/DUnitX and THTTPClient.

HashLoad/horse · 25 tokens

prompt-design

Design MCP prompts to expose reusable prompt templates. Use when creating parameterized prompts in xmcp.

basementstudio/xmcp · 22 tokens