module-mark-skill

module-mark-skill is a skill for Claude Code, Codex from yunzeforbetter/CastFlow. It costs 43 tokens per session (408 once invoked), scanned A, original, MIT.

A software-architecture workflow for deciding how candidate packages should be treated during a module split. It compares whether each package is a feature, shared method, independent system, or framework mechanism before proposing where it belongs.

In plain words
What is it for?
Use it to build evidence cards, review package relationships, choose actions such as attach or split, and show the resulting module cut before it is accepted.
Why use it?
It prevents module boundaries from being chosen from directory names alone or from unverified guesses. It also keeps unresolved decisions visible and records accepted marks for later scans.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to build evidence cards, review package relationships, choose actions such as attach or split, and show the resulting module cut before it is accepted.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yunzeforbetter/castflow/module-mark-skill
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 yunzeforbetter/CastFlow --skill module-mark-skill
Clone the repo
git clone --depth 1 https://github.com/yunzeforbetter/CastFlow

Made for: Claude Code, Codex.

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 module-mark-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/yunzeforbetter/castflow/module-mark-skill/github.svg)](https://agentmods.dev/skills/yunzeforbetter/castflow/module-mark-skill)
Your own site
<a href="https://agentmods.dev/skills/yunzeforbetter/castflow/module-mark-skill"><img src="https://agentmods.dev/badge/skills/yunzeforbetter/castflow/module-mark-skill/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 module-mark-skill

Your own site · 80×15
<a href="https://agentmods.dev/skills/yunzeforbetter/castflow/module-mark-skill"><img src="https://agentmods.dev/badge/skills/yunzeforbetter/castflow/module-mark-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 408 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.00043 $0.00408
Opus 5.5 $0.00017 $0.00163
Sonnet 5.5 $0.00009 $0.00082
Haiku 4.5 $0.00004 $0.00041

Measured 1mo ago against content hash 3af9260a15a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

module-mark-skill 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 1mo 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.

.castflow/core/skills/module-mark-skill/SKILL.md · 42 lines

What it actually says

Module marks

Mark packages so the module cut follows how this repo is built. The mark is a weight on an engineering stance. It is not a directory rule and not a skill.

Yield

  • One module's API how-to -> that programmer-*-skill
  • Drawing the package graph or printing the first cut -> coldstart
  • Designing a Jev question for some other job -> the jev skill, if installed
  • Writing scan ledgers (GRAPH.md, knowledge-graph.json, .ua/) -> never

Responsibilities

  1. Build one evidence card per candidate package from the scanner. Do not invent packages by reading files one by one.
  2. Score four stances: feature, shared method, independent system, framework mechanism. Use a structural prior always. When TYPESAFE_API_KEY is set, unresolved cards go to official TypeSafe System One (jev-latest unless TYPESAFE_DEFAULT_MODEL is set). When it is not set, say so and keep the prior. Do not invent a probability.
  3. Turn the winning stance into attach, split, keep, or review. Show the revised cut. Do not hide unmarked rows.
  4. Persist a mark only after the user accepts it. The next scan applies accepted marks before the prior and before Jev.
  • EXAMPLES.md — evidence card, Jev questions, cut actions
  • SKILL_MEMORY.md — what a mark is not allowed to do
  • ITERATION_GUIDE.md — when this skill changes
  • marks.schema.json — card and decision fields; read it when emitting marks
Files

What ships with it

4 files 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. 1mo ago First seen · 42 lines · 43 tokens per session scan A 3af9260a15a8

Subscribe to this mod's changes

module-mark-skill is a skill published in the GitHub repository yunzeforbetter/CastFlow (108 stars, last pushed 16d ago), licensed MIT. It adds 43 tokens to every session and 408 once invoked, about $0.0002 per session on Opus 5.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-09-24.

Related

Other skills, from other repositories

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

systematic-debugging

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

obra/superpowers · 21 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

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens