plan-v2-extract-domain

plan-v2-extract-domain is a skill for Claude Code from jakkaj/tools. It costs 40 tokens per session (3,353 once invoked), scanned A, original, MIT.

A guided workshop for naming and documenting a meaningful area of an existing codebase as a domain, such as authentication or billing. It records which files belong to that area without moving or refactoring them.

In plain words
What is it for?
Use it to inspect code related to a concept, catalogue its files and interfaces, agree on what is included, and write domain documentation.
Why use it?
It gives the team a shared name and clear boundaries for discussing related code that may currently be spread across many folders.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions subagents.

Good fit Use it to inspect code related to a concept, catalogue its files and interfaces, agree on what is included, and write domain documentation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jakkaj/tools/plan-v2-extract-domain
View source ↗ jakkaj/tools
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.

Any agent
npx skills add jakkaj/tools --skill plan-v2-extract-domain
Clone the repo
git clone --depth 1 https://github.com/jakkaj/tools

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 plan-v2-extract-domain

README.md
[![agentmods](https://agentmods.dev/badge/skills/jakkaj/tools/plan-v2-extract-domain/github.svg)](https://agentmods.dev/skills/jakkaj/tools/plan-v2-extract-domain)
Your own site
<a href="https://agentmods.dev/skills/jakkaj/tools/plan-v2-extract-domain"><img src="https://agentmods.dev/badge/skills/jakkaj/tools/plan-v2-extract-domain/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 plan-v2-extract-domain

Your own site · 80×15
<a href="https://agentmods.dev/skills/jakkaj/tools/plan-v2-extract-domain"><img src="https://agentmods.dev/badge/skills/jakkaj/tools/plan-v2-extract-domain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,353 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.00040 $0.03353
Opus 5 $0.00020 $0.01677
Sonnet 5 $0.00008 $0.00671
Haiku 4.5 $0.00004 $0.00335

Measured 9d ago against content hash 3b5b1e4fbbb2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

plan-v2-extract-domain 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 9d 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.

skills/SDD/plan-v2-extract-domain/SKILL.md · 411 lines

How it starts

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

Please deep think / ultrathink as this is a complex task.

extract-domain

Collaboratively identify and formalize an existing codebase concept as a named domain without moving files. This is a workshop with the user, not an automated refactor. The goal is communication — future plans can reference "the auth domain" and everyone knows what that means.

User input:

$ARGUMENTS
# Expected:
# <concept>                    — the concept to extract (e.g., "authentication", "billing")
# Optional flags:
# --domain <slug>              — override the auto-generated slug
# --list                       — list existing domains and exit

What This Command Does

  1. Explores the codebase to discover all code related to the concept
  2. Catalogues discovered files and their roles — presented to user for review
  3. Workshops with user to define what belongs vs. doesn't (boundary)
  4. Identifies public interfaces other code already consumes (contracts)
  5. Maps internal components (services, adapters, repos — composition)
  6. Writes docs/domains/<slug>/domain.md pointing to files where they currently live
  7. Updates docs/domains/registry.md (creates it if first domain)

What This Command Does NOT Do

  • ❌ Move files to a new directory structure
  • ❌ Refactor imports
  • ❌ Create new source directories
  • ❌ Change any code

Step 0: List Mode

If --list flag provided:

  • Read docs/domains/registry.md (if exists)
  • Display all registered domains with slug, type, status
  • If docs/domains/domain-map.md exists, show it too — the map gives the visual overview of how domains relate
  • If no registry exists, report "No domains registered yet"
  • Exit

Step 1: Check for Existing Domain

  • Read docs/domains/registry.md if it exists
  • Read docs/domains/domain-map.md if it exists — understand the current domain topology, existing contract relationships, and where a new domain might fit
  • Check if a domain with matching slug already exists
  • If exists: report it and ask user whether to update or abort
  • Generate slug from concept: lowercase, replace spaces with hyphens, strip non-alphanumeric

Read the full file on GitHub · 411 lines

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. 9d ago First seen · 411 lines · 40 tokens per session scan A 3b5b1e4fbbb2

Subscribe to this mod's changes

plan-v2-extract-domain is a skill published in the GitHub repository jakkaj/tools (5 stars, last pushed 23d ago), licensed MIT. It adds 40 tokens to every session and 3,353 once invoked, about $0.0002 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens