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 skills add yunzeforbetter/CastFlow --skill module-mark-skillgit clone --depth 1 https://github.com/yunzeforbetter/CastFlowWrote 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/yunzeforbetter/castflow/module-mark-skill)<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.
<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>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.00043 | $0.00408 |
| Opus 5.5 | $0.00017 | $0.00163 |
| Sonnet 5.5 | $0.00009 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
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.
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
jevskill, if installed - Writing scan ledgers (
GRAPH.md,knowledge-graph.json,.ua/) -> never
Responsibilities
- Build one evidence card per candidate package from the scanner. Do not invent packages by reading files one by one.
- Score four stances: feature, shared method, independent system, framework
mechanism. Use a structural prior always. When
TYPESAFE_API_KEYis set, unresolved cards go to official TypeSafe System One (jev-latestunlessTYPESAFE_DEFAULT_MODELis set). When it is not set, say so and keep the prior. Do not invent a probability. - Turn the winning stance into
attach,split,keep, orreview. Show the revised cut. Do not hide unmarked rows. - Persist a mark only after the user accepts it. The next scan applies accepted marks before the prior and before Jev.
Navigate
- 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
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.
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.
- 1mo ago First seen · 42 lines · 43 tokens per session scan A 3af9260a15a8
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.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
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…
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…