Borrowing it
Nothing to install: this file belongs to irehsrg/mappal-palworld. 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/irehsrg/mappal-palworld/main/CLAUDE.mdgit clone --depth 1 https://github.com/irehsrg/mappal-palworldWrote 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/instructions/irehsrg/mappal-palworld/claude-md)<a href="https://agentmods.dev/instructions/irehsrg/mappal-palworld/claude-md"><img src="https://agentmods.dev/badge/instructions/irehsrg/mappal-palworld/claude-md.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.1 | $0.03258 | $0.03258 |
| Opus 5 | $0.01629 | $0.01629 |
| Sonnet 5 | $0.00652 | $0.00652 |
| Haiku 4.5 | $0.00326 | $0.00326 |
Grade A, and why
mappal-palworld CLAUDE.md 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 8d 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MapPal — Palworld Base Blueprint Editor
A browser-based spatial editor for Palworld base layouts. Load a base blueprint exported from PalworldSaveTools, edit it in 3D, export it back. Build mega-bases out of game.
This tool never touches a .sav file. Save I/O is delegated entirely to
PalworldSaveTools (PST). We are a lens on its blueprint JSON, nothing more.
1. Why this exists
The Palworld save-editing ecosystem is mature but entirely tabular. Existing tools (PalworldSaveTools, palworld-save-pal, Palworld-Pal-Editor) present bases as lists of objects and map dots. None of them let you place a foundation in space.
The gap: there is no TerraMap for Palworld. That's what this is.
Prior art we depend on, not compete with:
deafdudecomputers/PalworldSaveTools— has Export Base →.json, Import Base, Clone Base (offset), Adjust Radius. This is our file format.cheahjs/palworld-save-tools— the underlying GVAS parser. Reference for structure semantics only; we do not call it.
2. Hard constraints
These are not negotiable. Violating any of them changes the project into a different, much worse project.
| # | Constraint | Why |
|---|---|---|
| C1 | No .sav parsing, reading, or writing. Ever. |
The save format changes with game updates and has broken tooling before (a v0.3.7 restructure is widely reported, though we haven't verified that specific claim). PST absorbs that maintenance burden; we don't. |
| C2 | No game assets in the repo. No meshes, textures, icons ripped from .pak. |
Legal. Distribution of Pocketpair assets is not ours to do. Gray-box proxies only. |
| C3 | Client-side only. No backend, no upload. Amended 2026-07-21 (Alex's call, deliberate): the optional community gallery (docs/GALLERY.md) uses a hosted backend (Supabase) for auth + storage. The editor remains fully client-side — parsing, editing, and export never touch a server; a blueprint leaves the machine only when the user explicitly clicks Publish/Save-to-account. With gallery env vars absent the app runs identically to pure-C3. Amended 2026-07-23: anonymous usage analytics (PostHog: feature-usage counts, error capture — see src/analytics.ts for the counts-and-flags-only contract) run alongside Vercel Analytics. Blueprint parsing, editing, and export still never touch a server. | Blueprints are user data. Also makes it free to host. |
| C4 | Never invent a schema field. | See §4. Every field name comes from a real export or it doesn't exist. |
| C5 | Round-trip fidelity is the top priority, above features. | An export that corrupts someone's base is worse than no tool. Load → export with zero edits must produce a semantically identical file. |
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.
- 8d ago First seen · 270 lines · 3,258 tokens per session scan A 51678d212a6d
mappal-palworld CLAUDE.md is an instructions file published in the GitHub repository irehsrg/mappal-palworld (5 stars, last pushed 6d ago), licensed MIT. It adds 3,258 tokens to every session, about $0.0163 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-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.