baud-cli AGENTS.md

Repository instructions for baud-cli, a tool for serial-device diagnostics and guarded hardware workflows. They define required checks and how to handle changes to its bundled skill.

In plain words
What is it for?
Use them when changing baud-cli, running its lint, formatting, and test checks, validating the bundled skill, or checking whether its installed copy is current.
Why use it?
They provide a consistent way to verify code and skill changes before committing them, reducing the chance of shipping untested hardware-related work.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/nitmi/baud-cli/agents-md
Clone the repo
git clone --depth 1 https://github.com/Nitmi/baud-cli

Made for: Codex, OpenCode.

Per session 100 This file is loaded in full into every session.
When invoked 100 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00100 $0.00100
Opus 5 $0.00050 $0.00050
Sonnet 5 $0.00020 $0.00020
Haiku 4.5 $0.00010 $0.00010

Measured yesterday against content hash 6c9ef583f64c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

baud-cli 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.

AGENTS.md · 7 lines

What it actually says

Repository Guidance

  • Commit cohesive, completed work at appropriate checkpoints after verification. Do not wait for an explicit commit request when a meaningful unit of work is finished.
  • Keep unrelated user changes out of a commit.
  • Before committing, run uv run ruff check ., uv run ruff format --check ., and uv run pytest.
  • When the bundled Skill changes, also run the skill validator and verify the user-level installed copy is either current or explicitly reported as stale.
Changes

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.

  1. yesterday First seen · 7 lines · 100 tokens per session scan A 6c9ef583f64c

Subscribe to this mod's changes

baud-cli AGENTS.md is an instructions file published in the GitHub repository Nitmi/baud-cli (5 stars, last pushed 22d ago), licensed MIT. It adds 100 tokens to every session, about $0.0005 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.

Related

Other instructions, from other repositories