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 tamdogood/builder-essential-skills --skill map-the-landscapegit clone --depth 1 https://github.com/tamdogood/builder-essential-skillsWrote 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/tamdogood/builder-essential-skills/map-the-landscape)<a href="https://agentmods.dev/skills/tamdogood/builder-essential-skills/map-the-landscape"><img src="https://agentmods.dev/badge/skills/tamdogood/builder-essential-skills/map-the-landscape/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/tamdogood/builder-essential-skills/map-the-landscape"><img src="https://agentmods.dev/badge/skills/tamdogood/builder-essential-skills/map-the-landscape.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00116 | $0.01833 |
| Opus 5 | $0.00058 | $0.00916 |
| Sonnet 5 | $0.00023 | $0.00367 |
| Haiku 4.5 | $0.00012 | $0.00183 |
Grade A, and why
map-the-landscape 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 11d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Map the Landscape
Build a useful mental model, not an exhaustive catalog. Reveal the structure that makes details make sense: what is inside the boundary, what sits outside it, which relationships matter, how value or data moves, why the landscape looks this way, and where uncertainty remains.
Set the Zoom
Infer these from the request and available context:
- Subject: the topic, field, ecosystem, or repository to map.
- Mode:
topic,repository, orhybridwhen a repo must be placed in its wider ecosystem. - Audience: the user's current knowledge and intended use.
- Decision: what the map should help the user understand or do next.
- Depth:
snapshot,standard, ordeep. - Time horizon: current state by default; add history when it explains the present.
Ask at most one clarifying question only when the subject or intended zoom is
genuinely ambiguous. Otherwise state the chosen boundary and proceed. Use
standard depth unless the user requests a quick overview or a deep study.
Evidence Discipline
Keep the map auditable without making it read like a research paper.
- Label important statements as Observed when read directly from repository files, Sourced when supported by an external source, Inferred when deduced from evidence, and Unknown when evidence is insufficient.
- For current or unstable topic claims, browse and cite authoritative sources. Prefer primary documentation, specifications, papers, repositories, release notes, and first-party material.
- For repository claims, inspect code and local documentation before relying on
summaries. Use
rg --files, manifests, entry points, configuration, tests, and recent history to learn the system's own vocabulary. - Do not present directory names, dependency lists, search snippets, stars, or popularity as explanations. Translate evidence into relationships and consequences.
- Distinguish the implemented system from stated intent. A README describes a promise; code paths and tests show what is enforced.
What ships with it
3 files 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.
- 11d ago First seen · 205 lines · 116 tokens per session scan A b729de98a8e6
map-the-landscape is a skill published in the GitHub repository tamdogood/builder-essential-skills (196 stars, last pushed 25d ago), licensed MIT. It adds 116 tokens to every session and 1,833 once invoked, about $0.0006 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-08-30.
Other skills, from other repositories
architecture-compass
Architectural thinking partner for an existing repository — scans the codebase, conducts a structured interview, agrees on current architectural state and recommended direction, and produces a shareable insights document. Scoped to one repository, module, or folder. Does not execute transformation — it orients. Use…
architecture-refiner
Facilitate a structured conversation to define architecture principles for a repository. Supports multiple architecture styles: clean architecture (default), hexagonal / ports & adapters, modular monolith, or custom. Produces a formal architecture document that the corresponding atom will use. Use when setting up a…
review-refiner
Facilitate a structured conversation to customize how the review molecule works -- atom loading rules, severity classification, report format, scope rules, insight capture, and health logging. Produces a formal review-standards.md document that the review molecule will use as its process configuration. Use when the…
skill-review
Deep behavioral audit of a Lattice skill — proposes 3 review personas relevant to the skill, runs independent scenario analysis from each persona's perspective, then merges only the high-confidence, practical findings into a severity-ordered gap report with proposed fixes. Structural validation (conventions…
clean-code-refiner
Facilitate a structured conversation to define clean code principles for a repository. Produces a formal clean-code.md document that the clean-code atom will use as its override. Use when setting up coding standards, defining code quality rules, or when the user says 'setup clean code', 'define coding standards'…
context-anchoring
Manage per-feature living documents that capture decisions, constraints, and reasoning across AI sessions during active development. Scoped to feature-level work — design, implementation, bugfix, refactor — not for codebase-wide assessments or product-wide specifications (those define their own document lifecycles).…