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/lommix/blitzdenk/agents-mdgit clone --depth 1 https://github.com/Lommix/blitzdenkWrote 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/lommix/blitzdenk/agents-md)<a href="https://agentmods.dev/instructions/lommix/blitzdenk/agents-md"><img src="https://agentmods.dev/badge/instructions/lommix/blitzdenk/agents-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.01101 | $0.01101 |
| Opus 5 | $0.00550 | $0.00550 |
| Sonnet 5 | $0.00220 | $0.00220 |
| Haiku 4.5 | $0.00110 | $0.00110 |
Grade A, and why
blitzdenk AGENTS.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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Blitzdenk
A coding harness written in Zig with vendored Lua. Zig version: 0.16
Important modules:
src/root.zigimport hub; everything is reached via ther.*namespacesrc/agent_id.zigAgentIdpacked struct{index: u16, generation: u16};pack()/unpack()bitcast to u32src/main.zigcontrol flow, owns the hot-reload loopsrc/app.zigmain tui state and render;applyRunEventturns stream events into chat previewsrc/tuitui lib and common widgetssrc/toolsagent tool definitionssrc/lua.zigthe lua bindings, big file; the wholeblitz.*api is one declarativeBlitztable_defsrc/mcp.zigthe mcp api and tools.src/context_factory.zigagent and prompt configuration; system prompt built per configureAgentsrc/skills.zigskill loading and managementsrc/exec.zigshell wrappersrc/keys.zigkey bindingssrc/models.zigmodel config;Modelunion over provider kinds ollama/openai/response/anthropicsrc/agent.zigthe agent state;Activityenum andobserve()derive status/stream statesrc/agent_run.zigrun task + event queue bridging sdk streams to observerssrc/agent_registry.zigstate management for many agents;drain()fans events outsrc/commands.zigasync command queue.src/inject.zigagent status injectionssrc/session.zigsave/load session state;SaveState/WireToolStatusshared by store checkpoint andblitz continuesrc/session_store.zigJSONL session journals in~/.cache/blitzdenk/<fnv1a64-of-cwd>/sessions/<id>.jsonl(header + full-snapshot checkpoints, cap 4, tmp+rename compaction, GC >16d);blitz continue [ID],blitz sessions(TUI session picker oversummaries()rows; widget state insrc/session_picker.zig, rendered like the wizard) and the exit hint inmain.ziguse it; debug.log also lives in~/.cache/blitzdenk;cacheDir()honorsXDG_CACHE_HOMEover~/.cachesrc/compact.zigchat compaction logicsrc/events.zigexposed hookssrc/defaults.ziginstalls default config files into~/.config/blitzdenksdk/the blitz-sdk ai provider librarysdk/src/provider/one file per provider:openai.zigchat completions,responses.zigResponses API,anthropic.zig,compat.zig;jsonx.zighttp + SSE plumbing
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 · 55 lines · 1,101 tokens per session scan A 21ca4d66c503
blitzdenk AGENTS.md is an instructions file published in the GitHub repository Lommix/blitzdenk (10 stars, last pushed 3d ago), licensed MIT. It adds 1,101 tokens to every session, about $0.0055 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
Albatross AGENTS.md
Instructions for morganlinton/Albatross, covering agent instructions, general and releases.
sail CLAUDE.md
Instructions for standardapplied/sail, covering claude.md, why sail exists, tech stack, infrastructure inside containers and conventions.
lunar AGENTS.md
Instructions for gszr/lunar, covering how to work here, our goals, before you type, code and scope.
superturtle CLAUDE.md
Instructions for Rigos0/superturtle, covering superturtle user notes, latest release highlights, important migration info, common commands and notes for the turtle.
wezterm-ai-agents CLAUDE.md
Instructions for nakashima-takeo/wezterm-ai-agents, covering claude.md, 概要, コマンド, lint and フォーマットチェック.
superturtle AGENTS.md
Instructions for Rigos0/superturtle, a project described as: Coding agent on your phone 🐢.