Borrowing it
Nothing to install: this file belongs to najaeda/naja-verilog. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/najaeda/naja-verilog/main/AGENTS.mdgit clone --depth 1 https://github.com/najaeda/naja-verilogWrote 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/najaeda/naja-verilog/agents-md)<a href="https://agentmods.dev/instructions/najaeda/naja-verilog/agents-md"><img src="https://agentmods.dev/badge/instructions/najaeda/naja-verilog/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.1 | $0.00456 | $0.00456 |
| Opus 5 | $0.00228 | $0.00228 |
| Sonnet 5 | $0.00091 | $0.00091 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
naja-verilog 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 6d 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.
What it actually says
Repository guidance
Build systems: CMake (primary) + Bazel (validated smoke test)
CMake is naja-verilog's primary build system. It is used by the main Ubuntu and macOS CI matrices, coverage, valgrind, CodeQL, Emscripten, installation, and normal development, and it is the build system to use by default:
cmake -S . -B build -DCMAKE_BUILD_TYPE=Debug
cmake --build build
ctest --test-dir build --output-on-failure
Bazel (MODULE.bazel, BUILD.bazel, and bazel/) is kept in parallel
as a validated smoke test. The additive ubuntu-bazel.yml and
macos-bazel.yml workflows run:
bazel build //...
bazel test //...
Those workflows do not initialize git submodules: bzlmod fetches googletest, while Bison, Flex, and M4 are resolved from the host. Bazel is not CI's primary gate and does not need to reproduce CMake-specific coverage, valgrind, sanitizer, CodeQL, Emscripten, or installation behavior. Its role is to prove that the native Bazel module still compiles and passes its tests, including when consumed by naja.
Keep the googletest pins synchronized
CMake uses the thirdparty/googletest git submodule, while Bazel uses
the googletest version in MODULE.bazel. Both must name the same
upstream release. ci/check_submodule_bazel_sync.py, run by
dependency-sync-check.yml, reads the CMake gitlink and verifies it
against the upstream tag corresponding to Bazel's module version.
After changing either pin, update the other in the same change and run:
python3 ci/check_submodule_bazel_sync.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.
- 6d ago First seen · 51 lines · 456 tokens per session scan A c8559a3e856b
naja-verilog AGENTS.md is an instructions file published in the GitHub repository najaeda/naja-verilog (42 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 456 tokens to every session, about $0.0023 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
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 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).
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.
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.