Borrowing it
Nothing to install: this file belongs to CodeBoarding/CodeBoarding-action. 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/CodeBoarding/CodeBoarding-action/main/AGENTS.mdgit clone --depth 1 https://github.com/CodeBoarding/CodeBoarding-actionWrote 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/codeboarding/codeboarding-action/agents-md)<a href="https://agentmods.dev/instructions/codeboarding/codeboarding-action/agents-md"><img src="https://agentmods.dev/badge/instructions/codeboarding/codeboarding-action/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/codeboarding/codeboarding-action/agents-md"><img src="https://agentmods.dev/badge/instructions/codeboarding/codeboarding-action/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.01247 | $0.01247 |
| Opus 5.5 | $0.00499 | $0.00499 |
| Sonnet 5.5 | $0.00249 | $0.00249 |
| Haiku 4.5 | $0.00125 | $0.00125 |
Grade A, and why
CodeBoarding-action 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 18d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — CodeBoarding-action
This repo is a GitHub Action with two modes, selected by the mode input:
mode: review(default): analyzes a PR with the CodeBoarding engine and posts a Mermaid diagram of the added, modified, and removed components as a PR comment (runs onpull_request/issue_comment).mode: sync: on push to the one branch its trigger lists, regenerates the analysis and saves the.codeboarding/state wherecodeboarding_analysis_locationsays (an orphancodeboarding/baselinebranch by default, orin_placeon that branch itself), so review mode always diffs against a current baseline.
The action is a thin orchestration wrapper, not the analysis engine: the engine
(CodeBoarding/CodeBoarding) is a separate repo checked out at runtime and
pinned to a release in action.yml. scripts/engine_adapter.py is the CLI
adapter into it (no analysis logic lives there). Engine changes reach users only
when that pin is bumped and a new action release ships.
Bumping the engine pin
scripts/action/supported-providers.json mirrors the pinned release's LLM_PROVIDERS.
Credentials are validated before the engine is installed — that is what makes a
misconfigured run fail in seconds instead of a minute — so the action cannot ask
the engine at run time and keeps this copy instead.
When you change the codeboarding== pin in action.yml, update that file in the
same commit: its engine field, and any provider whose selection variables
changed. tests/test_provider_table_drift.py runs in the core-compatibility CI
job and fails when they disagree. Adding a provider also means adding its
<name>_api_key input to action.yml; tests/test_action_inputs.py checks that.
Protected tests
Some tests encode a behavioural contract that is expensive to rediscover once
lost. They are marked with a PROTECTED TEST header naming what they protect.
No agent, assistant, or automated tool may edit, weaken, skip, rename or delete a protected test — not even to make a build pass. Only a human may change one, and only after explicitly saying so in that conversation. A request to "fix the failing tests" is not that consent.
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.
- 18d ago Changed · +4 lines · +59 tokens per session 1643f5cfd021
- 2mo ago First seen · 98 lines · 1,188 tokens per session scan A 50f827898946
CodeBoarding-action AGENTS.md is an instructions file published in the GitHub repository CodeBoarding/CodeBoarding-action (11 stars, last pushed yesterday), licensed MIT. It adds 1,247 tokens to every session, about $0.0050 per session on Opus 5.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-30.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.