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/det-lab/kaitai_struct_awkward_runtime/agents-mdgit clone --depth 1 https://github.com/det-lab/kaitai_struct_awkward_runtimeWrote 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/det-lab/kaitai_struct_awkward_runtime/agents-md)<a href="https://agentmods.dev/instructions/det-lab/kaitai_struct_awkward_runtime/agents-md"><img src="https://agentmods.dev/badge/instructions/det-lab/kaitai_struct_awkward_runtime/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.00995 | $0.00995 |
| Opus 5 | $0.00498 | $0.00498 |
| Sonnet 5 | $0.00199 | $0.00199 |
| Haiku 4.5 | $0.00100 | $0.00100 |
Grade A, and why
kaitai_struct_awkward_runtime 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/awkward_kaitai/: Python package (runtime, builder, reader, data). Public API lives here.tests/: Pytest suite (test_*.py) plus JSON fixtures.example_data/schemas/: Kaitai.ksyschemas used to generate C++ sources.test_artifacts/: Generated.cppfiles and compiled.solibraries (build outputs).kaitai_struct_compiler/: Kaitai Struct compiler submodule (Scala/SBT build).docs/,mkdocs.yml: Documentation site content and configuration.
Setup & Dependencies
- Initialize submodules first:
git submodule update --init --recursive. - Toolchain: Java + SBT for the compiler, CMake + C++ toolchain for building shared libs, Python 3.8+.
- Kaitai compiler requirement:
kaitai-struct-compiler0.11+ with theawkwardtarget.
Build, Test, and Development Commands
pip install -e .installs the package in editable mode.nox -s lintruns pre-commit hooks across the repo.nox -s pylintruns pylint on the package.nox -s testsruns the pytest suite.make testbuilds C++ test artifacts and runs all tests.make compile_test testcase=hello_worldrebuilds a single schema and runs its test.make cleanremoveslocal/,build/, andtest_artifacts/outputs.
Makefile Workflow (Detailed)
- Prereqs: Java + SBT for
kaitai_struct_compiler/, plus a working C++ toolchain and Python env. make cppbuilds Scala compiler jars (via SBT) and generatestest_artifacts/*.cppfromexample_data/schemas/*.ksy.make testruns the full pipeline: compile compiler → generate C++ → build shared libstest_artifacts/lib*.so→pytest.make compile_test testcase=<name>is the fast loop for a single schema (<name>must match a file inexample_data/schemas/).make cleanwipes generated artifacts and SBT build products; rerunmake testafter cleaning.
Coding Style & Naming Conventions
- Python formatting and linting are enforced by pre-commit (Black, Ruff, mypy, codespell).
- Indentation is 4 spaces; keep line length flexible (Ruff ignores E501).
- Tests are named
tests/test_*.py(enforced by pre-commit). - Prefer
from __future__ import annotationsfor new modules (Ruff isort rule).
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 · 61 lines · 995 tokens per session scan A 88dfab438888
kaitai_struct_awkward_runtime AGENTS.md is an instructions file published in the GitHub repository det-lab/kaitai_struct_awkward_runtime (2 stars, last pushed 3d ago), licensed MIT. It adds 995 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
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.