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/temikus/denkeeper/claude-mdgit clone --depth 1 https://github.com/Temikus/denkeeperWrote 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/temikus/denkeeper/claude-md)<a href="https://agentmods.dev/instructions/temikus/denkeeper/claude-md"><img src="https://agentmods.dev/badge/instructions/temikus/denkeeper/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 | $0.02975 | $0.02975 |
| Opus 5 | $0.01488 | $0.01488 |
| Sonnet 5 | $0.00595 | $0.00595 |
| Haiku 4.5 | $0.00298 | $0.00298 |
Grade A, and why
denkeeper 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 3d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code (claude.ai/code) when working in this repository.
Build & Development Commands
Tooling: just (user-facing) → Task (Taskfile.yml, per-target fingerprint caching, cache in gitignored .task/) → mise for tool pinning (.mise.toml: Go 1.26.5, swag 1.16.6 — swag pinned because its output is a committed, CI-gated artifact). Bust one step: mise x -- task <name> --force; bust the whole hook chain: JUST_HOOK_FORCE=1 just hook.
just build # Build binary → pkg/bin/denkeeper
just serve # Build UI, then serve dashboard + API on :8080 (live reload)
just dev # Backend :8080 + Vite dev server :5173 (hot reload)
just test # All Go tests with -race
just test-v # Verbose test output
just test-pkg internal/agent # Single package
just test-ui # Web UI tests (vitest)
just lint # golangci-lint
just fmt # gofmt -w .
just check # CI equivalent: fmt-check + vet + lint + test + test-ui + openapi-check
just hook # `just check`, minimal output, cached — prefer this for full-suite runs
just scan # gosec + govulncheck
just build-ui # Build web UI (auto-run by build/test/vet/lint when web/dist missing)
just build-full # Build web then binary
just openapi # Generate OpenAPI spec (requires swag CLI)
just openapi-check # Fail if the committed spec is stale (CI gate)
just dev-ui # Vite dev server only (hot reload)
just test-integration # E2E integration tests
Architecture
Denkeeper is a single-binary personal AI agent with multi-agent routing:
Adapter (Telegram/Discord) ─┐
Web Dashboard (WS/SSE) ─────┼→ Dispatcher → Engine (per agent) → LLM Router → Provider (Anthropic/OpenRouter/OpenAI/Ollama)
REST API (/api/v1/chat) ────┘ ↕ ↕
MemoryStore CostTracker
(SQLite) + Pricing Registry
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.
- 3d ago First seen · 137 lines · 2,975 tokens per session scan A feba4b97f7b3
denkeeper CLAUDE.md is an instructions file published in the GitHub repository Temikus/denkeeper (11 stars, last pushed 4d ago), licensed Apache-2.0. It adds 2,975 tokens to every session, about $0.0149 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
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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.