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 allemaar/open-skills --skill map-thisgit clone --depth 1 https://github.com/allemaar/open-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/allemaar/open-skills/map-this)<a href="https://agentmods.dev/skills/allemaar/open-skills/map-this"><img src="https://agentmods.dev/badge/skills/allemaar/open-skills/map-this/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/allemaar/open-skills/map-this"><img src="https://agentmods.dev/badge/skills/allemaar/open-skills/map-this.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 148 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00055 | $0.04325 |
| Opus 5 | $0.00028 | $0.02162 |
| Sonnet 5 | $0.00011 | $0.00865 |
| Haiku 4.5 | $0.00006 | $0.00432 |
Grade A, and why
map-this 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 9d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/map-this
Plan, audit, and organize one bounded folder, project, or vault into a navigable map graph — including structuring UNSTRUCTURED data: a pile of files with no organization is the native case (the SETTLE verdict), and ingestion flows end with data arriving mapped, never loose. Fires on the Handler's organize/housekeep phrases or explicit /map-this (Handler decision 2026-07-30: model invocation enabled — the safety boundary is inside the workflow, not at the door). The audit is read-only; no mutation occurs before a displayed plan and Handler selection. The first value is always a ZERO-WRITE assessment — the pre-flight verdict (ADOPT/OFFER/SETTLE/ASK per the map-rules elasticity section, Handler-confirmed) plus the findings and proposal table; changes happen only as selected rows.
Additional proposal classes this workflow owns: README care (OWNERSHIP FIRST: a generated, legal, templated, or M3-managed README is not casually editable — check before proposing anything; then assess the README; propose ADDITIVE improvements only — links-to-maps, hot points — preserving the author's prose, ordering, and voice; existing house convention statements are pre-flight evidence, and once Handler-confirmed they persist as rulings that suppress re-litigation permanently); House Rules authoring (create or revise the root map's House rules section; graduate it to <scope>-rules.md when earned); shortcuts, asked once (nominate hot-point candidates by labeled judgment, ask the Handler ONCE which nodes need fast access, persist selected answers in the scope contract); born-mapped creation (any new-file or ingestion flow proposes file + owning map + member section as ONE approved set).
Base kernel: load and obey map-rules — every rule there governs every phase here. This file adds the workflow, environment branches, authority matrix, and pilot rubric.
Environment branches
Resolve the branch in Phase 1 and state it in the plan. Decision procedure: the scope is a registered Lyt vault iff lyt vault info --by-path <path> resolves it (or .lyt/vault.yon exists at the vault root); Lyt operations are callable iff the lyt CLI answers on this machine; otherwise it is a non-Lyt vault (branch 3).
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.
- 9d ago First seen · 196 lines · 55 tokens per session scan A 20938a1ede3f
map-this is a skill published in the GitHub repository allemaar/open-skills (14 stars, last pushed 22d ago), licensed Apache-2.0. It adds 55 tokens to every session and 4,325 once invoked, about $0.0003 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
polis-protocol
Set up and run a self-improving, multi-vendor AI agent team with the Polis Protocol — a markdown polis/ folder where each agent is a citizen with a capability card, tasks are contracts routed to whoever has the best track record by a learning router, settled work files lessons that compound into team memory, and…
media
Skill "media" from ymxlx/polis-protocol, covering polis protocol: a self-optimizing city of agents, the core idea, when this skill is active, structure of a polis and the first thing to do every session.
_data
Skill "_data" from ymxlx/polis-protocol, covering polis protocol: a self-optimizing city of agents, the core idea, when this skill is active, structure of a polis and the first thing to do every session.
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
mcporter
List, auth, and call MCP servers/tools from the terminal.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.