map

map is a command for Claude Code from Everyone-Needs-A-Copilot/claude-copilot. It costs 0 tokens per session (1,118 once invoked), scanned A, original, MIT.

A codebase-mapping command that creates or refreshes a PROJECT_MAP.md file describing a project's structure and technology stack. The map is intended to help coding agents navigate the repository.

In plain words
What is it for?
Use it to document a repository's layout, detect its stack, or update an existing project map without replacing its architecture notes.
Why use it?
Agents and developers can waste time discovering folders, languages, frameworks, and package tools from scratch. A stored project map gives them a shared starting point and can preserve manual architecture notes when refreshed.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Part of the claude-copilot plugin — 72 skills, 17 commands, 17 agents, 4 hooks shipped together

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/everyone-needs-a-copilot/claude-copilot/map
Clone the repo
git clone --depth 1 https://github.com/Everyone-Needs-A-Copilot/claude-copilot

Made for: Claude Code.

Or install claude-copilot, the plugin that ships this one along with the rest of its 72 skills, 17 commands, 17 agents, 4 hooks.

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 map

README.md
[![agentmods](https://agentmods.dev/badge/commands/everyone-needs-a-copilot/claude-copilot/map.svg)](https://agentmods.dev/commands/everyone-needs-a-copilot/claude-copilot/map)
Your own site
<a href="https://agentmods.dev/commands/everyone-needs-a-copilot/claude-copilot/map"><img src="https://agentmods.dev/badge/commands/everyone-needs-a-copilot/claude-copilot/map.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,118 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.1 $0.00000 $0.01118
Opus 5 $0.00000 $0.00559
Sonnet 5 $0.00000 $0.00224
Haiku 4.5 $0.00000 $0.00112

Measured yesterday against content hash 4445b0de5192, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

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 yesterday.

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/map.md · 148 lines

How it starts

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

Map Codebase

Generate PROJECT_MAP.md with project structure analysis for efficient agent navigation.

Usage

  • /map - Generate new PROJECT_MAP.md
  • /map --refresh - Update existing map (preserves manual notes)

Step 1: Check for Refresh Mode

If PROJECT_MAP.md exists and --refresh wasn't specified, warn and exit:

  • "PROJECT_MAP.md already exists. Use /map --refresh to update."

If --refresh specified, preserve the "Architecture Notes" section for later.

Step 2: Detect Tech Stack

Run these bash commands to detect the technology stack:

echo "Detecting tech stack..."

# Node.js / TypeScript
if [ -f "package.json" ]; then
  echo "- Language: JavaScript/TypeScript"
  if [ -f "yarn.lock" ]; then echo "- Package Manager: yarn"
  elif [ -f "pnpm-lock.yaml" ]; then echo "- Package Manager: pnpm"  
  else echo "- Package Manager: npm"; fi
  
  # Framework detection
  if grep -q '"next"' package.json 2>/dev/null; then echo "- Framework: Next.js"
  elif grep -q '"react"' package.json 2>/dev/null; then echo "- Framework: React"
  elif grep -q '"vue"' package.json 2>/dev/null; then echo "- Framework: Vue"
  elif grep -q '"express"' package.json 2>/dev/null; then echo "- Framework: Express"
  fi
fi

# Rust
if [ -f "Cargo.toml" ]; then
  echo "- Language: Rust"
  echo "- Package Manager: cargo"
fi

# Go  
if [ -f "go.mod" ]; then
  echo "- Language: Go"
  echo "- Package Manager: go mod"
fi

# Python
if [ -f "requirements.txt" ] || [ -f "pyproject.toml" ]; then
  echo "- Language: Python"
  if [ -f "poetry.lock" ]; then echo "- Package Manager: poetry"
  elif [ -f "Pipfile" ]; then echo "- Package Manager: pipenv"
  else echo "- Package Manager: pip"; fi
fi

Step 3: Generate Directory Structure

# Use tree if available (preferred)
if command -v tree &> /dev/null; then
  tree -L 3 -I 'node_modules|dist|build|.git|__pycache__|.venv|target|vendor' --dirsfirst
else
  # Fallback to find
  find . -maxdepth 3 -type d \
    -not -path './node_modules/*' \
    -not -path './dist/*' \
    -not -path './.git/*' | sort
fi

Read the full file on GitHub · 148 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. yesterday First seen · 148 lines · 0 tokens per session scan A 4445b0de5192

Subscribe to this mod's changes

map is a command published in the GitHub repository Everyone-Needs-A-Copilot/claude-copilot (13 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,118 tokens. 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-04.

Related

Other commands, from other repositories

analytics

/analytics Show full analytics dashboard /analytics top Top 10 most-used agents /analytics failures Show agents with highest failure rates /analytics timeline Show invocation timeline (last 7 days) /analytics agent Show stats for a specific agent /analytics trends Show improving vs degrading agents over time…

samibs/skillfoundry · 0 tokens

explain

/explain Explain the last agent action (quick mode) /explain --verbose Full trace with file changes and decision rationale /explain --story STORY-XXX All actions for a story in chronological order /explain --agent Last action by a specific agent /explain --session All actions from a specific session /explain --diff…

samibs/skillfoundry · 0 tokens

feature

Role: Per-feature quality pipeline that takes a story or feature description from zero to a committed, documented, tested, and evaluated implementation. No stage is skipped. No commit happens without the evaluator's approval.

samibs/skillfoundry · 0 tokens

security-scanner

Security scanner specialized in detecting AI-generated code vulnerabilities using comprehensive anti-pattern databases. You are methodical, thorough, and uncompromising -- every vulnerability is documented, traced, and given a concrete fix.

samibs/skillfoundry · 0 tokens

swarm

You are the Swarm Coordination Manager: a disciplined parallel execution engine that decomposes work into independent units, dispatches them to isolated workers, monitors progress, detects conflicts, and aggregates results into a coherent whole. You turn serial bottlenecks into parallel throughput — safely.

samibs/skillfoundry · 0 tokens

data-architect

You are a rigorous data architect. You design schemas that scale, optimize queries that crawl, and normalize (or denormalize) with surgical precision. You do not accept "we'll optimize later" or "it works in dev" database design.

samibs/skillfoundry · 0 tokens