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/kunchenguid/chrome-devtools-axi/agents-mdgit clone --depth 1 https://github.com/kunchenguid/chrome-devtools-axiWrote 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/kunchenguid/chrome-devtools-axi/agents-md)<a href="https://agentmods.dev/instructions/kunchenguid/chrome-devtools-axi/agents-md"><img src="https://agentmods.dev/badge/instructions/kunchenguid/chrome-devtools-axi/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 | $0.04130 | $0.04130 |
| Opus 5 | $0.02065 | $0.02065 |
| Sonnet 5 | $0.00826 | $0.00826 |
| Haiku 4.5 | $0.00413 | $0.00413 |
Grade A, and why
chrome-devtools-axi 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 3d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to coding agents when working with code in this repository.
Commands
pnpm run build # tsc to dist/ + chmod the CLI entrypoint
pnpm run build:skill # Regenerate the minimal skills/chrome-devtools-axi/SKILL.md stub from src/skill.ts
pnpm run dev # Run the CLI from source with tsx
pnpm test # vitest run (test/*.test.ts)
pnpm run test:watch # vitest watch mode
Run a single test file: pnpm test test/cli.test.ts.
Filter by test name: pnpm test -- -t "formatStopOutput".
Check formatting with pnpm exec prettier --check ..
The committed skills/chrome-devtools-axi/SKILL.md is generated by pnpm run build:skill; pnpm test fails if it drifts from createSkillMarkdown().
Its body and frontmatter are owned by src/skill.ts; update the generator instead of hand-editing SKILL.md.
Project Conventions
- Node 20+, TypeScript, ESM-only (
"type": "module", module resolutionNode16- relative imports use.jsextensions even from.tsfiles). - Tests live in
test/*.test.tsand run with Vitest. - Run
pnpm run buildandpnpm testbefore pushing. - Do not hand-edit generated files:
CHANGELOG.mdand.release-please-manifest.json(owned by release-please) orskills/chrome-devtools-axi/SKILL.md(owned bybuild:skill). - Every
pull_requestworkflow (ci.yml,guard-generated-files.yml,no-mistakes-required.yml) usespaths-ignorefor the release-please output set (.release-please-manifest.json,CHANGELOG.md,package.json) so release PRs create zero runs. Job-level botifs stay as defense in depth.test/release-ci-exclusions.test.tsderives that set fromrelease-please-config.jsonand fails if a workflow drifts; update the ignore lists when addingextra-filesor changingrelease-type. - Generated files are listed in
.prettierignore; validate them with their generator checks instead of formatting them directly. - Keep
skills/chrome-devtools-axi/in the npmfileslist when changing package contents; the skill-first install path depends on it shipping with the package. pnpm-workspace.yamlenforces a minimum release age for dependency updates as a supply-chain guard;axi-sdk-jsandchrome-devtools-axiare exempt..airlock/lint.shmust use pnpm (nevernpm installornpx);test/airlock-lint.test.tsenforces this.- Human-authored PRs to
mainmust go throughno-mistakes(>= 1.46.0); the gate inno-mistakes-required.ymlrequires the body signature, theno-mistakes-pipeline-attestation:v1comment (review/test/document allcompleted), and the attestedhead_shato equal the PR's current head. See CONTRIBUTING.md. .github/workflows/no-mistakes-required.ymlis a thin caller of the sharedkunchenguid/no-mistakes/.github/actions/require-no-mistakescomposite action, pinned to an immutable commit SHA and never@main. Enforcement logic and its tests live upstream in the no-mistakes repository; change enforcement there rather than copying it back here, and bump this repository's pin in a deliberate separate PR. This repo still owns itson:,paths-ignore,concurrency,permissions, job name, and author-exemptionif:.- The gate runs on opened, edited, and reopened events, not on pushes. When one of those events runs, the shared action's head binding rejects a body that no-mistakes did not rewrite for the current head. That is the attestation contract, not a flake: push through
git push no-mistakesso the body is refreshed.
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.
- 3d ago First seen · 122 lines · 4,130 tokens per session scan A 057e26887deb
chrome-devtools-axi AGENTS.md is an instructions file published in the GitHub repository kunchenguid/chrome-devtools-axi (344 stars, last pushed 5d ago), licensed MIT. It adds 4,130 tokens to every session, about $0.0207 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-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).
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.
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.
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 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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.