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.
npx agentmods add skills/hirogakatageri/hirokata/split-plannpx skills add HirogaKatageri/hirokata --skill split-plangit clone --depth 1 https://github.com/HirogaKatageri/hirokataWrote 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.
[](https://agentmods.dev/skills/hirogakatageri/hirokata/split-plan)<a href="https://agentmods.dev/skills/hirogakatageri/hirokata/split-plan"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/split-plan.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00047 | $0.02882 |
| Opus 5 | $0.00023 | $0.01441 |
| Sonnet 5 | $0.00009 | $0.00576 |
| Haiku 4.5 | $0.00005 | $0.00288 |
Grade A, and why
split-plan 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.
How it starts
The opening of the file, as written. The whole thing — 409 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Split Plan
Transform a master plan into 8 phase-specific implementation plans organized by feature tracks with complexity scoring.
Purpose
Analyze a master plan file and generate 8 separate plan files, one for each phase of clean architecture (Foundational, Models, Services, Data, Rules, State Management, UI, Tests).
Overview
Analyze a master plan file and generate 8 separate plan files, one for each phase of clean architecture:
- Foundational - Base abstractions, utilities, infrastructure
- Models - Data entities, DTOs, value objects
- Services - External APIs, service integrations
- Data - Repositories, DAOs, local storage
- Rules - Business logic, use cases, validation
- State Management - ViewModels, presenters, state handlers
- UI - Screens, components, widgets
- Tests - Unit tests, integration tests, test utilities
Inputs
- Master Plan:
${master-plan-path}- The comprehensive plan to analyze - Base Name:
${base-name}- Prefix for all generated files
Outputs
Eight phase plan files in tasks/${base-name}/plans/:
${base-name}-01-foundational.md${base-name}-02-models.md${base-name}-03-services.md${base-name}-04-data.md${base-name}-05-rules.md${base-name}-06-state-management.md${base-name}-07-ui.md${base-name}-08-tests.md
Workflow
1. Analyze Master Plan
Read the master plan from ${master-plan-path} and:
Extract tasks: Identify all implementation tasks from the plan
- Look for numbered lists, bullet points, sections
- Extract task titles and descriptions
- Note dependencies and relationships
Identify feature tracks: Group related tasks by feature/module
- Use lowercase-with-hyphens naming (e.g., "authentication", "user-profile")
- Prefer broader groupings over granular ones
- Ensure tracks can span multiple phases
- Common tracks: authentication, products, cart, notifications, settings
Classify tasks by phase: Determine which phase each task belongs to
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.
- 5d ago First seen · 409 lines · 47 tokens per session scan A c6502baf74e9
split-plan is a skill published in the GitHub repository HirogaKatageri/hirokata (5 stars, last pushed 2d ago), licensed MIT. It adds 47 tokens to every session and 2,882 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.
Other skills, from other repositories
unslop
Humanize LLM output so it reads like a careful human wrote it. Subtracts AI-isms (sycophancy, tricolons, em-dash overuse, "delve"/"tapestry"/"testament", hedging stacks, tidy five-paragraph shapes), engineers burstiness and calibrated uncertainty, and preserves technical accuracy. Supports intensity levels: subtle…
unslop-file
Humanize natural-language memory files (CLAUDE.md, todos, preferences, docs) by removing AI-isms and adding burstiness while preserving every code block, URL, path, command, and heading exactly. Two modes: --deterministic (fast, regex-based, no API) and LLM (default, calls Claude for rewrite). Humanized version…
unslop-commit
Rewrites commit messages so they sound like a careful human engineer wrote them. Strips AI/marketing slop ("comprehensive solution", "robust implementation", "leverage", "enhance", "seamlessly", "This commit..."). Keeps Conventional Commits format. Subject ≤72 chars (aim ≤50), imperative mood. Body only when "why"…
unslop-help
Quick-reference card for unslop modes, sub-skills, and slash commands. One-shot display, not a persistent mode. Trigger: /unslop-help, "unslop help", "what unslop commands", "how do I use unslop".
simulator-smart-forms-logic
Author and evolve the Corezoid backend that powers a Simulator.Company Smart Form. Use whenever the user wants a Smart Form to do anything beyond a static layout — load dynamic viewModel data, react to submits, drive page-level changes, trigger notifications, write back to actors — OR wants to modify existing backend…
simulator-finance
Simulator.Company financial management specialist. Use when the user wants to manage financial and metric accounts on actors (balances, counters, plan vs fact), record transactions, transfer value between accounts, work with currencies and account-name categories, track non-financial metrics, read balances and…