What is epistemic-mapper?

A project knowledge map that sorts what the code and documentation show into proven facts, open questions, unwritten assumptions, and possible risks.

It helps prepare an evidence-based handoff by creating or updating a standard EPISTEMIC-MAP.md file.

It captures knowledge that may otherwise remain only in the original builder’s head, reducing surprises when another engineering team takes over a prototype.

epistemic-mapper — Skill for Claude Code and Codex by gohypergiant

Install

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.

Any agent

npx skills add gohypergiant/agent-skills --skill epistemic-mapper

Clone the repo

git clone --depth 1 https://github.com/gohypergiant/agent-skills

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/gohypergiant/agent-skills/epistemic-mapper/github.svg)](https://agentmods.dev/skills/gohypergiant/agent-skills/epistemic-mapper)

Your own site

<a href="https://agentmods.dev/skills/gohypergiant/agent-skills/epistemic-mapper"><img src="https://agentmods.dev/badge/skills/gohypergiant/agent-skills/epistemic-mapper/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/gohypergiant/agent-skills/epistemic-mapper"><img src="https://agentmods.dev/badge/skills/gohypergiant/agent-skills/epistemic-mapper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 200 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 5,353 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 2 findings, up to high

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 →

high Memory Poisoning · line 360
Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.

Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
medium Prompt Injection · line 3
Subtle instructions detected that may alter agent decision-making or introduce hidden biases.

Fix: Review content for implicit steering or bias. Ensure instructions are explicit and align with the skill's stated purpose.

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00200	$0.05353
Opus 5	$0.00100	$0.02677
Sonnet 5	$0.00040	$0.01071
Haiku 4.5	$0.00020	$0.00535

Measured 11d ago against content hash 257e82ec0cfd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

epistemic-mapper 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.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/merge_epistemic_map.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/epistemic-mapper/SKILL.md · 412 lines

How it starts

The opening of the file, as written. The whole thing — 412 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Epistemic Mapper

Extract a project's knowledge state from its documentation and its code, then sort every observation into one of four quadrants and write the result into a canonical EPISTEMIC-MAP.md. This is a handoff artifact: it exists because a prototype builder holds a mass of tacit knowledge that never got written down, and once a contract is signed and a team takes over, that knowledge either gets captured now or gets rediscovered the hard way, in production.

                    HIGH CERTAINTY (validated)
                              |
          [ ASSUMPTIONS ]    |    [ FACTS ]
          Unknown Known      |    Known Known
          nobody wrote it    |    proven, cited
          down, but the      |    evidence
          code/docs rely     |
          on it              |
    ------------------------ + ------------------------
                              |
          [ RISKS ]           |    [ QUESTIONS ]
          Unknown Unknown     |    Known Unknown
          blind spots, found  |    explicit open
          only by looking     |    gaps, already
          across everything   |    flagged somewhere
                              |
                    LOW CERTAINTY (unvalidated)

Relationship to Other Living Documents

CONSTRAINTS.md holds externally-imposed hard limits. JARGON.md holds term definitions. ARCHITECTURE.md holds structural decisions. AGENTS.md holds agent behavior and orchestration. EPISTEMIC-MAP.md is different in kind from all four: it isn't a ledger of what's true, it's a map of how sure we are about what's true. Read the other living docs (if present) before extraction starts, for two reasons:

Don't duplicate. If a Known Known is already stated in CONSTRAINTS.md or defined in JARGON.md, reference it by file and section instead of restating it as a new Fact. EPISTEMIC-MAP.md should point at the other living docs, not compete with them.
Seed confidence. A claim backed by an entry in CONSTRAINTS.md is about as validated as a claim gets — treat it as a Known Known with CONFIRMED confidence by default, not something to re-litigate.

Read the full file on GitHub · 412 lines

Files

What ships with it

7 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.

Changes

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 · 412 lines · 200 tokens per session scan A 257e82ec0cfd

Subscribe to this mod's changes

epistemic-mapper is a skill published in the GitHub repository gohypergiant/agent-skills (24 stars, last pushed yesterday), licensed Apache-2.0. It adds 200 tokens to every session and 5,353 once invoked, about $0.0010 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.

Planning

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens