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/kot149/zmk-layout-shift/agents-mdgit clone --depth 1 https://github.com/kot149/zmk-layout-shiftWhat 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.01018 | $0.01018 |
| Opus 5 | $0.00509 | $0.00509 |
| Sonnet 5 | $0.00204 | $0.00204 |
| Haiku 4.5 | $0.00102 | $0.00102 |
Grade A, and why
zmk-layout-shift 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 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
For detailed project overview, features, and usage instructions, please refer to README.md.
ZMK Development Guidelines
CRITICAL PREREQUISITES - MANDATORY BEFORE ANY IMPLEMENTATION CHANGES:
-
Consult the ZMK Repository Expert: Query the Deepwiki MCP server (repoName:
zmkfirmware/zmk) to understand the current implementation and identify potential issues. -
Consult the Zephyr Repository Expert: Since ZMK is Zephyr-based, also query the Deepwiki MCP server (repoName:
zephyrproject-rtos/zephyr) for Zephyr-specific implementation details when needed. -
Share Context: Provide the MCP server with:
- Current implementation details
- Identified problems or requirements
- Your proposed implementation approach
-
Validate Implementation Strategy: Confirm your implementation plan with the ZMK expert before proceeding.
-
Update Documentation: After making any changes, always update the README.md with relevant information about new features, usage instructions, or implementation status.
Why This Process is Essential:
- Pre-trained Knowledge Limitations: LLM training data may not reflect the latest ZMK architecture, APIs, or best practices
- Build Failure Prevention: ZMK has specific conventions and dependencies that may not be obvious from general knowledge
- Implementation Accuracy: The ZMK codebase has evolved significantly, and outdated approaches will likely fail
NO ASSUMPTIONS: Always verify current ZMK practices before implementation. What worked in older versions may not work in current releases.
EXPERT FIRST: Consult zmkfirmware/zmk and zephyrproject-rtos/zephyr repository experts before coding, not after encountering build failures.
Development Environment
Build and test instructions in this document assume development within zmk-workspace. Commands, paths, and just recipes may not work in other environments.
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 First seen · 87 lines · 1,018 tokens per session scan A a50338833a7f
zmk-layout-shift AGENTS.md is an instructions file published in the GitHub repository kot149/zmk-layout-shift (17 stars, last pushed 2d ago), licensed MIT. It adds 1,018 tokens to every session, about $0.0051 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-09-01.
Other instructions, from other repositories
zmk-config AGENTS.md
AGENTS.md instructions for urob/zmk-config, covering customization guide, ground rules, how the multi-board layout works, adding a new board and where to change what.
FastLED GEMINI.md
Gemini CLI instructions for FastLED/FastLED, a project described as: The FastLED library for colored LED animation on Arduino. Please direct questions/requests for help to the FastLED Reddit community: http://fastled.io/r We'd like to use github "issues" just for tracking library bugs / enhancements.
kicad-happy GEMINI.md
Instructions for aklofas/kicad-happy, covering kicad-happy, agent guidelines, skills, running analysis and schematic analysis.
brilliant_sdk AGENTS.md
Instructions for brilliantlabsAR/brilliant_sdk, covering brilliant sdk — agent guide, how an app works (the pattern behind everything), minimal reading paths, verify without hardware and testing.
NeoMind CLAUDE.md
Instructions for camthink-ai/NeoMind, covering neomind — edge ai platform for iot, development commands, ecosystem repositories, extension package contract (.nep) and device type template contract (json).
Nothan-OS CLAUDE.md
Instructions for Vinalinux-Org/Nothan-OS, covering claude.md — nothanos, hard rules, toolchain, driver and design philosophy.