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 pwdev-solucoes/pwdev-claude-marketplace --skill feat-mapgit clone --depth 1 https://github.com/pwdev-solucoes/pwdev-claude-marketplaceWrote 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/pwdev-solucoes/pwdev-claude-marketplace/feat-map)<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.
<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>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.00106 | $0.00786 |
| Opus 5.5 | $0.00042 | $0.00314 |
| Sonnet 5.5 | $0.00021 | $0.00157 |
| Haiku 4.5 | $0.00011 | $0.00079 |
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.
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
- Language — resolve
lang(references/language.md). - Scan —
python3 "<plugin-root>/scripts/feat_map.py" --repo-root . --write. Report thesource_commit, the previous map's staleness andexcluded_sensitive. Commands in the output are evidence only — never run them. - 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.
- Dependency audit (optional) — ask the human before running
npm audit/composer audit/ equivalent (they may hit the network). Declined → recordn/a. - Write from
templates/context/*.mdandtemplates/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(includingtests_dir,e2e_scenarios_dir,e2e_generated_dirand the real commands),concerns.md;.planning/feat/codebase.md— the one-screen index (kept for 2.x compatibility).
- Record:
sh "<plugin-root>/scripts/audit-log.sh" event map "" completed .planning/feat/context/. - 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.
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.
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.
- 27d ago First seen · 56 lines · 106 tokens per session scan A e7f9692382a8
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.
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…
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…
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.
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.