agentmods.dev

classify

A command that records how difficult and uncertain a coding task is before code is changed. It uses the Cynefin framework, a way to classify work as clear, complicated, complex, chaotic, or needing clarification.

In plain words
What is it for?
Use it before editing code to classify the task and record how many different concerns it touches.
Why use it?
It gives the team and later checks a shared view of how much investigation and design the task requires.

Command

6 yesterday A scan 0 tokens original Apache-2.0
View the source file kouroshez/coding-os
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/kouroshez/coding-os/classify
Clone the repo
git clone --depth 1 https://github.com/kouroshez/coding-os
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 441 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00000 $0.00441
Opus 5 $0.00000 $0.00220
Sonnet 5 $0.00000 $0.00088
Haiku 4.5 $0.00000 $0.00044

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

Security

Grade A, and why

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

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.

src/core/commands/classify.md · 24 lines

What it actually says

Record the Complexity Gate (Cynefin × dimensions) for the current task before any code edit.

The Complexity Gate is mandatory per Rule 7 and core/rules/thinking_os.md. It tells future hooks + reviewers what cognitive depth this task warrants. Skip → enforce-skill.sh may block edits on COMPLICATED+ paths.

Steps:

  1. If $ARGUMENTS is provided in the form Q1 Q2 (e.g. COMPLICATED 3), use it directly. Otherwise infer from the conversation:
    • Q1 (Cynefin): CLEAR (known fix) | COMPLICATED (known type, needs design) | COMPLEX (unknown answer, needs experiment) | CHAOTIC (broken now, act first) | CONFUSION (decompose first).
    • Q2 (dimensions): integer count of distinct concerns this task touches (auth + DB + UI = 3).
  2. State your classification + one-sentence rationale.
  3. Persist via the canonical gate writer — write-state.sh (the same hook the kernel rule's Record Gate documents). Replace .claude / claude with your adapter dir (.codex / codex for Codex): 
    bash .claude/hooks/write-state.sh .coding-os/claude/.thinking_os-gate "<Q1> <Q2>"
    This writes $COS_AGENT_DIR/.thinking_os-gate and unblocks downstream skill/edit hooks.
  4. If Q1 is COMPLICATED or COMPLEX, invoke Skill thinking_os for the full Zoom cycle.
  5. If Q1 is CHAOTIC, treat as an incident — load Skill incident-response, stabilize first.

Output format:

Classification: <Q1> <Q2>
Rationale: <one sentence>
Next step: <Plan | Zoom cycle | Incident stabilization>
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 · 24 lines · 0 tokens per session scan A e3d1588e7442

Subscribe to this mod's changes

classify is a command published in the GitHub repository kouroshez/coding-os (6 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 441 tokens. 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.

LanguagesPlanningai-agentsclaude-codecodexdeveloper-toolsknowledge-graphmcp
Related

Other commands, from other repositories

release-notes

Draft curated release notes for a milestone release.

RoboFinSystems/robosystems · 9 tokens

create-issue

Create a GitHub issue from the repo's templates, with the right type and labels.

RoboFinSystems/robosystems · 18 tokens

export

Export a knowledge abstract to an Obsidian vault — a folder of Markdown notes linked by [[wikilinks]].

yifanfeng97/Hyper-Extract · 0 tokens

wh:graph-review

Use when you want a Wheeler graph quality audit (wrong types, broken paths, dupes, stale nodes) with suggested fixes.

maxwellsdm1867/wheeler · 30 tokens

wh:asta-lit

Use when the user wants to find literature with Asta Paper Finder and ingest the results into the Wheeler knowledge graph.

maxwellsdm1867/wheeler · 27 tokens

soc2-review

Assess SOC 2 readiness against the Trust Services Criteria and produce a readiness dashboard.

RoboFinSystems/robosystems · 16 tokens