vulyk-map

vulyk-map is a command for Claude Code from Black-coffe/vulyk. It costs 15 tokens per session (207 once invoked), scanned A, original, MIT.

A command that creates or refreshes a map of a codebase, showing its main modules and where important code is located. It uses scout batches to inspect directories and stores short map files.

In plain words
What is it for?
Use it on a repository or directory to identify top-level modules, record module summaries, update memory pointers, and report areas that still need mapping.
Why use it?
It reduces the time spent discovering an unfamiliar repository and preserves earlier findings by checking existing maps for changes.

Command for Claude Code

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.

agentmods
npx agentmods add commands/black-coffe/vulyk/vulyk-map
Clone the repo
git clone --depth 1 https://github.com/Black-coffe/vulyk

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 vulyk-map

README.md
[![agentmods](https://agentmods.dev/badge/commands/black-coffe/vulyk/vulyk-map.svg)](https://agentmods.dev/commands/black-coffe/vulyk/vulyk-map)
Your own site
<a href="https://agentmods.dev/commands/black-coffe/vulyk/vulyk-map"><img src="https://agentmods.dev/badge/commands/black-coffe/vulyk/vulyk-map.svg" alt="Measured on agentmods" height="20"></a>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 207 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00015 $0.00207
Opus 5 $0.00008 $0.00103
Sonnet 5 $0.00003 $0.00041
Haiku 4.5 $0.00002 $0.00021

Measured 4d ago against content hash 21402ae44201, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

vulyk-map 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 4d 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.

.claude/commands/vulyk-map.md · 13 lines

What it actually says

Map target: "$ARGUMENTS"

  1. Resolve the target to concrete directories. For ".", list top-level modules and map breadth-first (load-bearing first).
  2. Dispatch drone-scout per module, up to 4 in parallel. Existing map files: pass the old file to the scout and ask for a delta-verify rather than a from-scratch rewrite (cheaper, preserves accumulated gotchas).
  3. Save reports as memory/map/<module>.md, set last-verified: <today>. Enforce the ~80-line cap - maps are indexes, not documentation.
  4. Update memory/memory.md pointers for new modules; keep the index <= 60 lines.
  5. Report: modules mapped, modules still unmapped, anything a scout flagged as surprising (those are wiki-note candidates).
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. 4d ago First seen · 13 lines · 15 tokens per session scan A 21402ae44201

Subscribe to this mod's changes

vulyk-map is a command published in the GitHub repository Black-coffe/vulyk (2 stars, last pushed 14d ago), licensed MIT. It adds 15 tokens to every session and 207 once invoked, about $0.0001 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.