feat-map

feat-map is a skill for Claude Code, Codex from pwdev-solucoes/pwdev-claude-marketplace. It costs 106 tokens per session (786 once invoked), scanned A, original, Apache-2.0.

A read-only codebase mapping workflow that scans a project and writes documents describing its structure, architecture, coding conventions, and testing setup. A codebase is the collection of source files and configuration that make up a project.

In plain words
What is it for?
Use it to inspect modules, representative files, project instructions, and test configuration, then update the project context documents used by planning.
Why use it?
It provides evidence-based project context without reading every file or changing source code. This helps planning work when the existing map is missing or out of date.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the pwdev-feat plugin — 13 skills, 8 commands shipped together

Good fit Use it to inspect modules, representative files, project instructions, and test configuration, then update the project context documents used by planning.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pwdev-solucoes/pwdev-claude-marketplace/feat-map
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 pwdev-solucoes/pwdev-claude-marketplace --skill feat-map
Clone the repo
git clone --depth 1 https://github.com/pwdev-solucoes/pwdev-claude-marketplace

Made for: Claude Code, Codex.

Or install pwdev-feat, the plugin that ships this one along with the rest of its 13 skills, 8 commands.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-map/github.svg)](https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-map)
Your own site
<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-map"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-map/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 feat-map

Your own site · 80×15
<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-map"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-map.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 106 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 786 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.00106 $0.00786
Opus 5.5 $0.00042 $0.00314
Sonnet 5.5 $0.00021 $0.00157
Haiku 4.5 $0.00011 $0.00079

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

Security

Grade A, and why

feat-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 27d 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.

plugins/pwdev-feat/skills/feat-map/SKILL.md · 56 lines

How it starts

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

Map the codebase

Contract: references/mapping.md. The scanner owns traversal, secret exclusion and determinism; you own interpretation and the context documents. Read-only on source code.

Procedure

  1. Language — resolve lang (references/language.md).
  2. Scan — python3 "<plugin-root>/scripts/feat_map.py" --repo-root . --write. Report the source_commit, the previous map's staleness and excluded_sensitive. Commands in the output are evidence only — never run them.
  3. Interpret — sample 2–3 representative files per module kind (entry points, a controller/handler, a service, a model, a component, a test) and read the style and test configs listed by the scan. Read the project instructions file if present. Do not read the whole repository.
  4. Dependency audit (optional) — ask the human before running npm audit / composer audit / equivalent (they may hit the network). Declined → record n/a.
  5. Write from templates/context/*.md and templates/codebase.md, keeping headings and keys; every claim cites its evidence path(s) and a confidence:
    • .planning/feat/context/architecture.md, conventions.md, testing.md (including tests_dir, e2e_scenarios_dir, e2e_generated_dir and the real commands), concerns.md;
    • .planning/feat/codebase.md — the one-screen index (kept for 2.x compatibility).
  6. Record: sh "<plugin-root>/scripts/audit-log.sh" event map "" completed .planning/feat/context/.
  7. Summary:
    🗺️ Codebase mapped at {short commit}
    Stack: {summary} | Pattern: {pattern} ({confidence})
    Size: {N} files, {N} modules | Tests: {frameworks} ({N} files) | E2E: {playwright|none}
    Risk areas: {top 3}
    📁 .planning/feat/codebase.md + context/{architecture,conventions,testing,concerns}.md
    👉 Next: feat-setup (if no project instructions file) or feat-feature "description"
    

Prohibitions

  • Never modify project source files — the only writes are under .planning/feat/.
  • Never read secrets (the scanner skips them; do not open them by hand either) or copy any secret value into the documents.
  • Never state a convention without an evidence path.

Read the full file on GitHub · 56 lines

Files

What ships with it

1 file 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. 27d ago First seen · 56 lines · 106 tokens per session scan A e7f9692382a8

Subscribe to this mod's changes

feat-map is a skill published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (3 stars, last pushed 10d ago), licensed Apache-2.0. It adds 106 tokens to every session and 786 once invoked, about $0.0004 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-28.

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

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 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

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.

microsoft/vscode · 53 tokens