ase-code-dissect

A workflow for breaking a large Git change set into cohesive parts, with each part placed in its own Git worktree. A worktree is a separate working folder connected to the same repository.

In plain words
What is it for?
Decomposing a large change into smaller, separately committable pieces.
Why use it?
It separates unrelated changes so they can be reviewed, developed, and committed independently.

Skill for Claude CodeCodex

View the source file rse/ase
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 skills/rse/ase/ase-code-dissect
Any agent
npx skills add rse/ase --skill ase-code-dissect
Clone the repo
git clone --depth 1 https://github.com/rse/ase

Made for: Claude Code, Codex.

Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,167 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.00074 $0.04167
Opus 5 $0.00037 $0.02083
Sonnet 5 $0.00015 $0.00833
Haiku 4.5 $0.00007 $0.00417

Measured 2d ago against content hash 84bd3fcedb92, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ase-code-dissect 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 2d 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.

plugin/skills/ase-code-dissect/SKILL.md · 402 lines

How it starts

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

@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md

$ARGUMENTS

@${CLAUDE_SKILL_DIR}/../../meta/ase-common-dissect.md

Procedure

    1. Determine the dissection hint: set , with any leading and trailing whitespace stripped. Additionally, inherit the always existing from the current context, as it names the worktrees and branches of all derived parts.

    2. Determine the repository root by running the corresponding command (taken exactly as given) and capturing its output into :

      git rev-parse --show-toplevel

    3. Determine the diff details and the diff statistics by running the corresponding commands (taken exactly as given) and capturing their full outputs into and :

      git diff --cached --numstat HEAD git diff

      git diff --numstat

    4. git -C "<repo-root/>" -c core.quotepath=off ls-files --others --exclude-standard

      Skip every listed entry below the .ase/ directory -- it carries ASE's own state and the worktrees created by this very skill, and hence is never part of the user's change set.

      Then, for every remaining listed file, capture its creation diff by running the corresponding command (taken exactly as given) and append its output to :

      git -C "<repo-root/>" diff --no-index --binary /dev/null "<file/>"

      This command intentionally exits with a non-zero status, because the two compared paths differ; treat this exit status as success, not as an error. Judge the outcome by the output instead: a run which emits no diff on standard output but an error: or fatal: message (e.g. the entry is a nested Git repository, which git ls-files reports as a directory) is a real failure -- append nothing for that entry and only output the following , then continue with the next file:

Read the full file on GitHub · 402 lines

Files

What ships with it

1 file 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. 2d ago First seen · 402 lines · 74 tokens per session scan A 84bd3fcedb92

Subscribe to this mod's changes

ase-code-dissect is a skill published in the GitHub repository rse/ase (47 stars, last pushed 4d ago), licensed Apache-2.0. It adds 74 tokens to every session and 4,167 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-30.

Related

Other skills, from other repositories