Borrowing it
Nothing to install: this file belongs to kuhumcst/DanNet. 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/kuhumcst/DanNet/master/CLAUDE.mdgit clone --depth 1 https://github.com/kuhumcst/DanNetWrote 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/kuhumcst/dannet/claude-md)<a href="https://agentmods.dev/instructions/kuhumcst/dannet/claude-md"><img src="https://agentmods.dev/badge/instructions/kuhumcst/dannet/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.00576 | $0.00576 |
| Opus 5 | $0.00288 | $0.00288 |
| Sonnet 5 | $0.00115 | $0.00115 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
DanNet 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 2d 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.
What it actually says
- Clojure is a FUNCTIONAL programming language.
- i.e. I expect you to do to REPL-based development in a FUNCTIONAL style.
- So when testing newly developed code, please just do a few relevant function calls in the REPL.
- i.e. I expect you to do to REPL-based development in a FUNCTIONAL style.
- Be surgical in your edits.
- I generally favour clean and lean git diffs over large refactors of the namespace(s).
- IMPORTANT: if you encounter something UNUSUAL (e.g. weird output or unexpected errors), report back immediately to me!
- Don't go on a longer tangent trying to analyze an unexpected error yourself (unless it is trivial to do so).
- You may start or restart the web service via the REPL (e.g.
(service/restart)) when the task calls for it — e.g. when setting up the environment or when a change genuinely requires a restart.- For routine fixes, still prefer testing in an isolated way using the REPL rather than restarting.
- After editing CLJ or CLJC files, reload the affected namespaces using
(require '[namespace] :reload)so the changes take effect in the running REPL. - For frontend-only bugs (hydration errors, CLJS/CLJ differences, CSS/layout issues), debug in the LIVE BROWSER via the shadow-cljs nREPL rather than guessing from source — follow the
browser-repl-debugskill (it loads on demand). - REPL access: use the
clj-nrepl-evalcommand to evaluate Clojure code via nREPL.- Discover running nREPL servers with
clj-nrepl-eval --discover-ports. - Evaluate with
clj-nrepl-eval -p <port> "<clojure-code>"(JVM nREPL: port 7888 via the:nreplalias; shadow-cljs runs its own auto-discoverable nREPL port). - REPL sessions persist per port: namespaces and state are maintained between evaluations.
- Discover running nREPL servers with
- When writing, editing, or reviewing Clojure code, follow the
clojure-styleskill (it loads on demand). - Database (re)builds:
bootstrap/other/holds manually curated source files that are NOT fetched automatically; the COR files (cor*.tsv,*.cordiff,cor.sem.*.tsv) can be re-downloaded from https://ordregister.dk/files/ if missing.- If a DB build fails partway, delete the half-built
db/tdb2/<db-name>directory (the path is in the build error's:data) before restarting —->dannetonly checks that the directory exists and will otherwise silently reuse the incomplete database ("Skipping build").
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.
- 2d ago Changed · +3 lines · +158 tokens per session 84cf2312edff
- 7d ago First seen · 17 lines · 418 tokens per session scan A b2303048e38e
DanNet CLAUDE.md is an instructions file published in the GitHub repository kuhumcst/DanNet (29 stars, last pushed 3d ago), licensed MIT. It adds 576 tokens to every session, about $0.0029 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 instructions, from other repositories
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).
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.
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.
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).
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.