Borrowing it
Nothing to install: this file belongs to PackmindHub/packmind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PackmindHub/packmind/main/.agents/skills/product-map/SKILL.mdgit clone --depth 1 https://github.com/PackmindHub/packmindWrote 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/packmindhub/packmind/product-map)<a href="https://agentmods.dev/skills/packmindhub/packmind/product-map"><img src="https://agentmods.dev/badge/skills/packmindhub/packmind/product-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/packmindhub/packmind/product-map"><img src="https://agentmods.dev/badge/skills/packmindhub/packmind/product-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.00091 | $0.02232 |
| Opus 5.5 | $0.00036 | $0.00893 |
| Sonnet 5.5 | $0.00018 | $0.00446 |
| Haiku 4.5 | $0.00009 | $0.00223 |
Grade A, and why
product-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 1mo 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Map
Build a point-in-time functional map of the Packmind application by scanning the backend (use cases + endpoints), the frontend (routes + pages), and the CLI (commands). Aggregate features by functional domain, compute a usage signal per feature, and write a single Markdown report at product-map.md (project root). The report supports decommission decisions: features with weak signals (no frontend entry, no recent activity, no tests) become candidates for removal.
Manual-only. Run only when the user explicitly invokes /product-map or asks for a functional cartography. The description above intentionally avoids generic trigger keywords.
This skill only maps — it does not delete anything. Decommission decisions stay with the user.
Phase 0: Confirm Scope
Before scanning, confirm with the user:
- Target output path — default
product-map.mdat project root; offer to override. - Scope override — default scans
apps/api,apps/frontend,apps/cli, andpackages/*. Ask if any package should be excluded (e.g., infra-only packages likemigrations,logger,node-utils). - Decommission tolerance — confirm signal heuristics (see Phase 4); user may want stricter or looser flagging.
If the user invoked the skill with explicit instructions, skip confirmation and proceed with stated parameters.
Phase 1: Seed Domain Taxonomy
Before launching subagents, read packages/ and apps/ to discover the domain taxonomy. Use folder names as the seed list — do NOT invent domains.
The seed domains in this codebase (verify by ls packages/ at run time, this list may drift):
- Spaces —
packages/spaces,packages/spaces-management - Standards —
packages/standards,packages/linter,packages/linter-ast,packages/linter-execution - Skills —
packages/skills - Recipes / Playbooks —
packages/recipes - Change Proposals —
packages/playbook-change-applier,packages/playbook-change-management - Users / Auth / Organizations —
packages/accounts - AI Agents / Coding Agent —
packages/coding-agent - Git Integration —
packages/git - Analytics —
packages/amplitude - Support / Crisp —
packages/crisp - Deployments —
packages/deployments - LLM Infrastructure —
packages/llm - Legacy Import —
packages/import-practices-legacy
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.
- 1mo ago First seen · 190 lines · 91 tokens per session scan A 0d349238950f
product-map is a skill published in the GitHub repository PackmindHub/packmind (319 stars, last pushed 4d ago), licensed Apache-2.0. It adds 91 tokens to every session and 2,232 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-22.
Other skills, from other repositories
ce-compound
Document a recently solved problem or durable project vocabulary in docs/solutions/ or CONCEPTS.md. Use when capturing a learning after work.
ce-work
Execute a plan or concrete work prompt end-to-end. Use when implementing from docs/plans, a spec path, or a clear build request; use ce-debug for open-ended bugs.
sdd
Execute the Liatrio Spec-Driven Development (SDD) workflow when explicitly invoked by the user. NOTE: this skill is NOT intended to be dynamically loaded or automatically triggered; it should only ever be explicitly called by the user.
loadout-import-workflow
Import another repo's command/skill suite into loadout as a workflow. Use when the user points at an agent framework, plugin, or command pack (e.g. a GitHub repo, a .claude/commands/ directory, a skills pack) and wants its process turned into a loadout [[workflows]] entry — "import this workflow", "turn this plugin…
ce-commit-push-pr
Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
loadout-migrate
Migrate existing global AI agent instructions into loadout. Use when adopting loadout, importing a CLAUDE.md / AGENTS.md / global agent rules into loadout, setting up /.config/loadout/config.toml, or turning prose agent instructions into reusable fragments and stack-targeted profiles.