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 agentmods add skills/matrixages/polywise/agentmap-generatornpx skills add MatrixAges/polywise --skill agentmap-generatorgit clone --depth 1 https://github.com/MatrixAges/polywiseWrote 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/matrixages/polywise/agentmap-generator)<a href="https://agentmods.dev/skills/matrixages/polywise/agentmap-generator"><img src="https://agentmods.dev/badge/skills/matrixages/polywise/agentmap-generator.svg" alt="Measured on agentmods" 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 | $0.00048 | $0.00302 |
| Opus 5 | $0.00024 | $0.00151 |
| Sonnet 5 | $0.00010 | $0.00060 |
| Haiku 4.5 | $0.00005 | $0.00030 |
Grade A, and why
agentmap-generator 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 today.
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.
What it actually says
Agentmap Generator
Update the package's agentmap.md whenever package structure or core responsibility boundaries change.
Keep the map faithful to disk:
- Re-scan the actual package tree before editing the map.
- Do not invent files, folders, or responsibilities.
- Exclude transient or protected folders such as names starting with
__.
Keep the map at outline level:
- Prefer top-level folders and major business subdomains.
- Stop at 1-2 levels deep in most packages.
- Use a third level only for large, stable coordination roots such as runtime kernels or data layers.
- Do not enumerate routine leaf files, repeated component atoms, or generated outputs.
Keep descriptions short:
- Describe folders by responsibility, not implementation detail.
- Mention files only when they are entry points, public coordinators, or important infrastructure roots.
- Prefer a few stable ownership statements over exhaustive file-by-file noise.
Keep the structure stable:
- Use a fenced
jsonblock for the tree. - Preserve existing top-level sections when they are still valid.
- Update both the tree and the prose summary when responsibilities changed.
Before finishing, verify that every changed package with an agentmap.md still matches the current outline on disk.
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.
- today First seen · 36 lines · 48 tokens per session scan A 1ac834944b7d
agentmap-generator is a skill published in the GitHub repository MatrixAges/polywise (659 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 302 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
artifact-deploy
One-click deploy a user's pre-built app/artifact into their OWN AWS account and get a global public HTTPS link (Vercel-like), with a default TTL and promote-to-persistent. Use when the user says "deploy this", "ship this demo", "give me a public link", "share this externally", or "deploy to AWS".
explain-for
Explain a topic, a piece of code, an error, or a design decision calibrated to one named audience — a 5-year-old, a 5th grader, a manager, a designer, a graduate student, a parent. Resolves who the explanation is for (from the request, or from what memory already records about that person), establishes the ground…
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
agent-initialization
Initialize an Agent's settings from a user requirement by writing AGENTS.md, setting identity metadata, and installing only needed Skills.
session-summaries
What the chat right-panel session summary shows, what it costs, and how to make a session summarize well. Load when the user asks about the session summary panel, why a summary looks wrong or empty, or how to turn it on.
pr-integration-test
Design, implement, and validate Intelligent Terminal integration tests for a target pull request or regression. Use when asked to add PR integration tests, convert a bug fix into E2E coverage, prove existing behavior still works, map tests to the release checklist, or verify E2E reports mark checklist cases complete.