Agent skill

Type Breakdown

Maps a code path's types, abstractions, data flow, side effects, and errors.

MITAuto-check passed

Install Type Breakdown

skills CLI

$ npx skills add iurysza/module-graph --skill type-breakdown -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install iurysza/module-graph type-breakdown --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/iurysza/module-graph.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/type-breakdown .claude/skills/type-breakdown && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "type-breakdown" agent skill from https://github.com/iurysza/module-graph/tree/main/.agents/skills/type-breakdown into .claude/skills/type-breakdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "type-breakdown", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/iurysza/module-graph/tree/main/.agents/skills/type-breakdown

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add iurysza/module-graph --skill type-breakdown -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install iurysza/module-graph type-breakdown --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iurysza/module-graph.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/type-breakdown .agents/skills/type-breakdown && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "type-breakdown" agent skill from https://github.com/iurysza/module-graph/tree/main/.agents/skills/type-breakdown into .agents/skills/type-breakdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "type-breakdown", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add iurysza/module-graph --skill type-breakdown -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install iurysza/module-graph type-breakdown --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iurysza/module-graph.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/type-breakdown .cursor/skills/type-breakdown && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "type-breakdown" agent skill from https://github.com/iurysza/module-graph/tree/main/.agents/skills/type-breakdown into .cursor/skills/type-breakdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "type-breakdown", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/iurysza/module-graph.git --path .agents/skills/type-breakdown

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add iurysza/module-graph --skill type-breakdown -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install iurysza/module-graph type-breakdown --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iurysza/module-graph.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/type-breakdown .gemini/skills/type-breakdown && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "type-breakdown" agent skill from https://github.com/iurysza/module-graph/tree/main/.agents/skills/type-breakdown into .gemini/skills/type-breakdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "type-breakdown", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install iurysza/module-graph type-breakdown

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add iurysza/module-graph --skill type-breakdown -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/iurysza/module-graph.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/type-breakdown .github/skills/type-breakdown && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "type-breakdown" agent skill from https://github.com/iurysza/module-graph/tree/main/.agents/skills/type-breakdown into .github/skills/type-breakdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "type-breakdown", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add iurysza/module-graph --skill type-breakdown -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install iurysza/module-graph type-breakdown --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iurysza/module-graph.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/type-breakdown .opencode/skills/type-breakdown && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "type-breakdown" agent skill from https://github.com/iurysza/module-graph/tree/main/.agents/skills/type-breakdown into .opencode/skills/type-breakdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "type-breakdown", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: type-breakdown
GitHub stars: 419
Token cost: ~844 tokens
SKILL.md length: 254 words
Files: 1
Skills in repo: 16
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Maps a code path's types, abstractions, data flow, side effects, and errors.

Works in 5 steps: Proposed functions and type signatures → Type ownership by file or module → Existing code that must change → …
Explicitly asks for a type breakdown of a feature
SKILL.md covers Execution Tree, Type Flow, Type Definitions and Error Flow, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Type Breakdown is an agent skill from iurysza/module-graph. Maps a code path's types, abstractions, data flow, side effects, and errors. Use only when the user explicitly asks for a type breakdown of a feature, flow, or code path.

Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: A Gradle Plugin for visualizing your project's structure, powered by mermaidjs. The licence is MIT.

When your agent uses it

Explicitly asks for a type breakdown of a feature

Example prompts

“/type-breakdown”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Proposed functions and type signatures
Type ownership by file or module
Existing code that must change
New files or abstractions required
Unresolved design questions

What it can do on your machine

Read from SKILL.md and the folder at commit 15b0135. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Type Breakdown loads about 844 tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 254 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~46
When it runs · the whole SKILL.md, loaded when a task matches: ~844

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from iurysza/module-graph at commit 15b0135, republished under its MIT licence (© iurysza). 254 words, ~844 tokens.

Download SKILL.mdSave it as .claude/skills/type-breakdown/SKILL.md (or your agent's skills folder).

name: type-breakdown
description: Maps a code path's types, abstractions, data flow, side effects, and errors. Use only when the user explicitly asks for a type breakdown of a feature, flow, or code path.
metadata.category: development

Type Breakdown

Walk the user through the requested code paths, types, abstractions, and data flow.

Turn a broad plan into a concrete, type-driven implementation outline. Prefer pseudocode, type signatures, and execution structure over PRD-style prose.

Inspect the existing code before proposing new abstractions.

If the subject is simple, keep the walkthrough concise. Otherwise, use the structure below as a reference. Do not follow it rigidly when a section does not apply.

Use these markers:

text

[existing]  Confirmed in the codebase
[inferred]  Implied by the current implementation
[proposed]  Introduced by this plan
[?]         Unresolved

Execution Tree

Start from the entry point and expand the call path recursively in execution order.

For every relevant call, show:

Fully qualified function, method, class, or module name
File where it is defined
Parent file and call site
Responsibility
Input and output types
Data transformations
Side effects
Possible errors
Child calls

Use this format:

text

▼ [existing] CheckoutController.create
  defined: src/checkout/api/CheckoutController.ts:24
  input:   CreateCheckoutRequest
  output:  Promise<HttpResponse<CreateCheckoutResponse>>

  └─▶ [existing] CreateCheckout.execute
      defined: src/checkout/application/CreateCheckout.ts:18
      called:  CheckoutController.ts:42
      input:   CreateCheckoutCommand
      output:  Result<Checkout, CreateCheckoutError>
      effects: reads customer, writes checkout

      ├─▶ CustomerRepository.find
      ├─▶ Checkout.create
      └─▶ CheckoutRepository.save

Use × N for repeated calls over collections. Do not invent line numbers when they are unavailable.

Type Flow

Show how data becomes progressively more constrained:

text

unknown
  → CreateCheckoutRequest
  → CreateCheckoutCommand
  → ResolvedCheckoutInput
  → Checkout
  → CheckoutRow
  → CreateCheckoutResponse

Identify the validation or transformation responsible for each transition.

Type Definitions

Provide pseudocode definitions for the important boundary, application, domain, persistence, state, and error types.

type CreateCheckoutCommand = {
  customerId: CustomerId;
  items: NonEmptyArray<CheckoutItemInput>;
};

type CreateCheckoutError =
  | { type: "CustomerNotFound"; customerId: CustomerId }
  | { type: "InvalidCheckout"; cause: CheckoutValidationError }
  | { type: "PersistenceFailure"; cause: PersistenceError };

Prefer domain-specific types over primitive strings and numbers when they encode identity, validation, units, or invariants.

Error Flow

Show where each error originates and how it is mapped and propagated:

text

UniqueConstraintViolation
  → PersistenceError.Conflict
  → CreateCheckoutError.PersistenceFailure
  → HTTP 409

Implementation Outline

Finish with:

Proposed functions and type signatures
Type ownership by file or module
Existing code that must change
New files or abstractions required
Unresolved design questions

Keep the output concrete, source-aware, and directly reviewable as an implementation plan.

Files

Just SKILL.md in .agents/skills/type-breakdown of iurysza/module-graph.

Open the folder on GitHubat commit 15b0135

Compare with similar skills

Type Breakdown next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Type Breakdown compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Type Breakdown this skilliurysza/module-graph	419	—	~844	Automated safety check: Pass	MIT	yesterday
Type Map Keeperdiscord-php/DiscordPHP	1.1k	—	~2.9k	Automated safety check: Pass	MIT	2 days ago
Rust Path Typesopeninterpreter/openinterpreter	69k	2 repos	~605	Automated safety check: Pass	Apache-2.0	yesterday
Type Mapping Encyclopediarevfactory/harness-100	1.3k	—	~1.7k	Automated safety check: Pass	Apache-2.0	6 mo ago
Python Type Safetywshobson/agents	40k	—	~1.4k	Automated safety check: Pass	MIT	3 days ago
Typescript Advanced Typesrolling-scopes/rsschool-app	10k	25 repos	~4.2k	Automated safety check: Pass	MPL-2.0	4 days ago

Similar skills

Type Map Keeper
discord-php/DiscordPHP
Maintain TYPES maps and subtype dispatch — Channel::TYPES, Interaction::TYPES, Component types, and related constants.
1.1k GitHub stars~2.9k tokensUpdated 2 days ago
Auto-check passed
Rust Path Types
openinterpreter/openinterpreter
Rules for choosing Rust types for filesystem paths in new Codex code, covering protocol types, internal use and model tool arguments.
69k GitHub starsUsed in 2 repos~605 tokens
DevelopmentAuto-check passed
Type Mapping Encyclopedia
revfactory/harness-100
RDBMS-to-RDBMS data type mapping tables, RDBMS-to-NoSQL conversion patterns, character set/collation conversion, and special type handling guide.
1.3k GitHub stars~1.7k tokensUpdated 6 mo ago
DatabasesAuto-check passed
Python Type Safety
wshobson/agents
Python type safety with type hints, generics, protocols, and strict type checking.
40k GitHub stars~1.4k tokensUpdated 3 days ago
DevelopmentAuto-check passed
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
10k GitHub starsUsed in 25 repos~4.2k tokens
DevelopmentAuto-check passed
Pyrefly Type Coverage
pytorch/pytorch
Migrate a file to use stricter Pyrefly type checking with annotations required for all functions, classes, and attributes.
104k GitHub stars~3k tokensUpdated today
DevelopmentAuto-check passed

Questions about Type Breakdown

What does Type Breakdown do?

Maps a code path's types, abstractions, data flow, side effects, and errors. Type Breakdown is an agent skill from iurysza/module-graph. Maps a code path's types, abstractions, data flow, side effects, and errors.

When should I use Type Breakdown?

Type Breakdown fits situations like: explicitly asks for a type breakdown of a feature.

How do I install Type Breakdown in Claude Code?

Run `npx skills add iurysza/module-graph --skill type-breakdown -a claude-code`. Or copy the skill folder (.agents/skills/type-breakdown in iurysza/module-graph) into .claude/skills/type-breakdown in your project. Claude Code loads it when a task matches its description.

How do I install Type Breakdown in Codex?

Run `npx skills add iurysza/module-graph --skill type-breakdown -a codex`. Or copy the skill folder (.agents/skills/type-breakdown in iurysza/module-graph) into .agents/skills/type-breakdown in your project. Codex loads it when a task matches its description.

Can I use Type Breakdown in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add iurysza/module-graph --skill type-breakdown -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/type-breakdown, .gemini/skills/type-breakdown, .github/skills/type-breakdown and .opencode/skills/type-breakdown in your project.

What does Type Breakdown need to run?

SKILL.md names no scripts, command-line tools or credentials: Type Breakdown is instructions for the agent only.

Does Type Breakdown access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Type Breakdown safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Type Breakdown use?

Type Breakdown is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Type Breakdown use?

About 844 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Type Breakdown?

Skills that share tags, products or a category with Type Breakdown: Type Map Keeper (discord-php/DiscordPHP, 1.1k stars), Rust Path Types (openinterpreter/openinterpreter, 69k stars), Type Mapping Encyclopedia (revfactory/harness-100, 1.3k stars) and Python Type Safety (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Type Breakdown?

iurysza (a GitHub user) maintains it in iurysza/module-graph, which has 419 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 7, 2026.

Source: iurysza/module-graph on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Type Breakdown

Install Type Breakdown

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Type Breakdown

Execution Tree

Type Flow

Type Definitions

Error Flow

Implementation Outline

Files

Compare with similar skills

Similar skills

Type Map Keeper

Rust Path Types

Type Mapping Encyclopedia

Python Type Safety

Typescript Advanced Types

Pyrefly Type Coverage

More from iurysza/module-graph

Audio Transcribe

Chatgpt Imagegen

Gemini Tts

Skill Cleaner

Brainstorming

Domain Modeling

Questions about Type Breakdown