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/byte-naut/npu-vision-fallback/claude-mdgit clone --depth 1 https://github.com/Byte-Naut/npu-vision-fallbackWrote 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/byte-naut/npu-vision-fallback/claude-md)<a href="https://agentmods.dev/instructions/byte-naut/npu-vision-fallback/claude-md"><img src="https://agentmods.dev/badge/instructions/byte-naut/npu-vision-fallback/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.01799 | $0.01799 |
| Opus 5 | $0.00899 | $0.00899 |
| Sonnet 5 | $0.00360 | $0.00360 |
| Haiku 4.5 | $0.00180 | $0.00180 |
Grade A, and why
npu-vision-fallback 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 5d 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.
This is a copy
95% identical to npu-vision-fallback AGENTS.md — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Project Constitution
⚠️ Archived (2026-08-01): no longer actively developed. This document remains as the historical engineering record for the experiment.
This file is read by AI coding assistants (Claude Code, Codex, OpenCode) to understand the constraints of this project. Violating these principles requires updating this document and explicit maintainer approval.
It also serves as the day-to-day guide for build/test commands and the high-level architecture. Read it fully before making changes.
Core Principles
-
Local-first. All inference must run locally. No cloud API calls except in explicit
examples/remote_*.pydemos. -
GPU-avoidant. By default, code paths must NOT wake up discrete GPUs. Prefer NPU > CPU > System OCR > dGPU.
-
Lightweight core. Core dependencies must not include
torch,torchvision,paddlepaddle, ortensorflow. These stay optional. (See Known Deviations for the currentultralyticsexception.) -
Backend-optional.
openvino,ultralytics,rapidocr_onnxruntime, and the Windowswinrt-*packages must all be gracefully import-guarded. A missing backend means fallback, not crash. -
No screenshot persistence. Never write screenshots to disk by default. Logs must not include OCR text content (privacy).
-
Coordinate integrity. OCR/detection backends return backend-local coordinates; the
Orchestratoris solely responsible for remapping to absolute screen coordinates. Don't double-shift. -
Fail loudly, degrade gracefully. An unavailable backend should log a warning and fall through to the next. Never silently return an empty result with
ok=Truewhen the real backend is broken. -
Test invariants. All tests must pass on Linux CI (using
dummy/rapid_ocr). Platform-specific tests are gated by pytest marks:windows_only,macos_only,npu_required. -
One tool = one responsibility. Adding a new MCP tool requires updating the README,
tests/, and the tool'sinputSchemainmcp_server.py.
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.
- 5d ago First seen · 162 lines · 1,799 tokens per session scan A 7712cb42ef85
npu-vision-fallback CLAUDE.md is an instructions file published in the GitHub repository Byte-Naut/npu-vision-fallback (1 stars, last pushed 1mo ago), licensed MIT. It adds 1,799 tokens to every session, about $0.0090 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to npu-vision-fallback AGENTS.md, differing in 5 lines, and is treated as a copy.
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.
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.
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 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).
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.