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 instructions/xyver/daedal-map/claude-mdgit clone --depth 1 https://github.com/xyver/daedal-mapWrote 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/xyver/daedal-map/claude-md)<a href="https://agentmods.dev/instructions/xyver/daedal-map/claude-md"><img src="https://agentmods.dev/badge/instructions/xyver/daedal-map/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.01004 | $0.01004 |
| Opus 5 | $0.00502 | $0.00502 |
| Sonnet 5 | $0.00201 | $0.00201 |
| Haiku 4.5 | $0.00100 | $0.00100 |
Grade A, and why
daedal-map 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 yesterday.
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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
County Map - Public Repo Instructions
Rules for working inside county-map/, the public application repo. This file
holds durable rules only, not a map of the codebase.
For architecture, request lifecycle, and which doc owns what, read docs/CONTEXT.md first. That is the start-here router and it stays current. Do not use this file for orientation.
This repo is public
Everything here is world-readable. Data processing scripts, internal planning, business docs, and operational runbooks belong in the private repo, not here.
Research and search
When asked to read, research, search, or investigate something, do it completely before answering or building. Partial reads that agree with each other feel like coverage and are not.
Docs before code. Start at docs/CONTEXT.md, the start-here router. Follow every route it names for the topic, not just the first one that matches the immediate question - the owning doc usually names the owning code and the known gaps.
Read to the end. Do not stop when the immediate question is answered. Ownership tables, change procedures, and "remaining gaps" sections sit at the bottom of a doc, and those are the parts that say whether the thing you are about to build already exists.
Finish the search before concluding. Do not cap a discovery search with
head and treat the result as the inventory - results sort alphabetically, so
a cap silently hides whatever sorts late. Either take the full list, or count it
first and say out loud that you are looking at a sample.
Search by concept, not by guessed implementation. The thing that already
exists may be a .md, .json, or .csv rather than the .py you assumed.
Search all file types before concluding nothing owns a job.
Assume an owner exists. Before writing a new script, table, or mapping, find the current owner and extend it. A parallel path that duplicates an existing one is worse than no change.
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.
- yesterday Changed · +31 lines · +322 tokens per session ff27d2276526
- 5d ago First seen · 91 lines · 682 tokens per session scan A 32b5a74e53d7
daedal-map CLAUDE.md is an instructions file published in the GitHub repository xyver/daedal-map (2 stars, last pushed today), licensed MIT. It adds 1,004 tokens to every session, about $0.0050 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
geolens CLAUDE.md
Claude Code instructions for geolens-io/geolens: This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
cpf-validador CLAUDE.md
Claude Code instructions for opastorello/cpf-validador, covering claude.md, comandos, rodar localmente (fastapi + fastmcp na porta 8000), docker (porta 8002 conforme docker-compose.yaml) and arquitetura.
substack-gateway-oss CLAUDE.md
Claude Code instructions for jakub-k-slys/substack-gateway-oss, covering claude.md, commands, install dependencies (dev included, all workspace members), run the server (dev mode with reload) and lint.
Huntable-CTI-Studio AGENTS.md
AGENTS.md instructions for dfirtnt/Huntable-CTI-Studio, covering agents.md, orientation, local context, prompt-injection alerting and change-type quick reference.
deckforge CLAUDE.md
Instructions for Whatsonyourmind/deckforge, covering deckforge, tech stack, project structure, key commands and local development.
Axon developer.instructions.md
Instructions for jyunming/Axon, covering role: developer, core conventions, document schema — never deviate, config.yaml → dataclass mapping and adding a new loader.