mellos-mapping

mellos-mapping is a skill for Claude Code from GuangminJu/mellos-mapping. It costs 120 tokens per session (2,896 once invoked), scanned A, original, MIT.

A live dependency map for building software from lower-level pieces upward. It records planned, active, and completed parts of a system in layered pages.

In plain words
What is it for?
Use it to declare planned components, track their progress, update the map as implementation changes, and inspect the current project structure.
Why use it?
It makes dependencies and unfinished work visible during larger tasks involving multiple modules or layers.

Skill for Claude Code

Written for Claude Code: SessionStart hook event. Also seen: mentions Claude Code; mentions Codex.

Part of the mellos-mapping plugin — 1 skill, 1 command, 1 hook, 1 MCP server shipped together

Good fit Use it to declare planned components, track their progress, update the map as implementation changes, and inspect the current project structure.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/guangminju/mellos-mapping/mellos-mapping
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 GuangminJu/mellos-mapping --skill mellos-mapping
Clone the repo
git clone --depth 1 https://github.com/GuangminJu/mellos-mapping

Made for: Claude Code.

Or install mellos-mapping, the plugin that ships this one along with the rest of its 1 skill, 1 command, 1 hook, 1 MCP server.

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 mellos-mapping

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/guangminju/mellos-mapping/mellos-mapping"><img src="https://agentmods.dev/badge/skills/guangminju/mellos-mapping/mellos-mapping.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 120 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,896 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.00120 $0.02896
Opus 5 $0.00060 $0.01448
Sonnet 5 $0.00024 $0.00579
Haiku 4.5 $0.00012 $0.00290

Measured 10d ago against content hash 9906c1d7ef68, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

mellos-mapping 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 10d 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/mellos-mapping/SKILL.md · 203 lines

How it starts

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

Mellos Mapping — the map discipline

Five MCP tools (mmap_declare, mmap_update, mmap_remove, mmap_view, mmap_setup) maintain a Mellos map: a layered dependency map of the system under construction, persisted in .mellos/map.json (default page) plus .mellos/pages/<slug>.json (named pages) and rendered live in a terminal split pane beside the conversation. To learn whether a map already exists — and under which page slugs — call mmap_view: every response ends with a pages: line naming the pages this project has and which one you are looking at. Never probe the default file to decide: it is absent whenever all work lives on named pages.

The map is a ledger, not a judge: the tools only refuse structural corruption; when to declare, start, or complete nodes is YOUR discipline, spelled out here. Report honestly — an unflattering map is doing its job.

When to open a map

The USER chooses how eager mapping is — once, for themselves, not once per project. In Claude Code the answer is already in this session's context: a SessionStart hook reads it and states it before the conversation begins, so there is nothing to probe. In hosts without hooks (Codex CLI, a bare MCP client) call mmap_setup with no arguments before the first map decision of the session; the reply names both scopes and which one governs.

  • always — map every structured task: workflows, designs, architecture, technical dependencies. Small effort, small map — but a map.
  • complex — map only medium or complex tasks: several interacting modules, a new subsystem, layered refactoring — roughly an hour of work or more. Skip trivial edits; a map of one node is noise. When unsure, ask.
  • on-request — open a map only when the user explicitly asks.

Under always and complex, the recorded policy is STANDING CONSENT: on a task it covers, declare the ghost design and open the pane yourself, without asking first. Re-asking for permission the user has already given is the failure mode this policy exists to remove.

Read the full file on GitHub · 203 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. 10d ago First seen · 203 lines · 120 tokens per session scan A 9906c1d7ef68

Subscribe to this mod's changes

mellos-mapping is a skill published in the GitHub repository GuangminJu/mellos-mapping (10 stars, last pushed 13d ago), licensed MIT. It adds 120 tokens to every session and 2,896 once invoked, about $0.0006 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.