What is tree-sitter-analyzer AGENTS.md?

A project instruction file for the tree-sitter-analyzer codebase, a tool that analyzes source code using Tree-sitter parsers. It explains where to find design maps and how to run tests and verification.

Use it when modifying tree-sitter-analyzer, especially its architecture, command-line options, language support, MCP tools, formatters, or security boundaries.

It helps coding agents inspect the right parts of the repository and follow the project’s required testing and change-checking process.

tree-sitter-analyzer AGENTS.md — Instructions file by aimasteracc

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/aimasteracc/tree-sitter-analyzer/agents-md

Clone the repo

git clone --depth 1 https://github.com/aimasteracc/tree-sitter-analyzer

Made for: Codex, OpenCode.

Per session 3,260 This file is loaded in full into every session.

When invoked 3,260 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.

Model	Per session	Once invoked
Fable 5	$0.03260	$0.03260
Opus 5	$0.01630	$0.01630
Sonnet 5	$0.00652	$0.00652
Haiku 4.5	$0.00326	$0.00326

Measured 3d ago against content hash 8f5450295d5e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tree-sitter-analyzer 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.

AGENTS.md · 145 lines

How it starts

The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Instructions

Discovery path: read this file → skim CLAUDE.md for the locked design decisions → load only the docs/CODEMAPS/ map matching the area you're touching. Do not load the full source tree blindly — the codemaps exist to keep agent context lean.

Codemap Index

Area	Codemap
High-level topology	`docs/CODEMAPS/architecture.md`
MCP tools (count in codemap)	`docs/CODEMAPS/mcp-tools.md`
CLI flags / commands	`docs/CODEMAPS/cli.md`
Language plugins (count in codemap)	`docs/CODEMAPS/languages.md`
Output formatters	`docs/CODEMAPS/formatters.md`
Security boundary	`docs/CODEMAPS/security.md`

Test Runtime Contract

The default full-suite command is uv run pytest -q.
Do not run the full suite serially. Project pytest config enables xdist with --numprocesses=auto --dist=loadfile.
The full suite must finish in under 5 minutes. The config enforces --session-timeout=900 and --timeout=30. (Bumped from 300 in v1.13.1 — see docs/POSTMORTEM_v1.13.md § 9.)
After edits, run uv run python -m tree_sitter_analyzer --change-impact --format json and follow its verification_command.
If test_required is false, do not run tests just to look busy; run the reported non-test verification such as git diff --check.
For targeted code feedback, prefer verification_command/test_command; pytest_required and pytest_command are retained for pytest-specific compatibility.
For PRs that change Python source, run focused tests with --cov=tree_sitter_analyzer --cov-report=json, then run uv run python scripts/check_patch_coverage.py --base origin/develop --coverage-json coverage.json before pushing. The local patch gate must report no added executable misses; add effective tests instead of waiting for CI Codecov to block the PR.
Benchmark-only runs are the exception: use uv run pytest tests/benchmarks/ --benchmark-enable --benchmark-only -n 0 --session-timeout=0.
Do not remove or weaken these pytest defaults. They prevent repeated agent mistakes: serial full-suite runs, accidental benchmark execution, hidden hangs, and >5 minute feedback loops.
If a test-runtime setting must change, update tests/contracts/test_pytest_runtime_contract.py, explain why the new setting is faster or safer, and prove uv run pytest -q still finishes under 5 minutes.

Read the full file on GitHub · 145 lines

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.

3d ago First seen · 145 lines · 3,260 tokens per session scan A 8f5450295d5e

Subscribe to this mod's changes

tree-sitter-analyzer AGENTS.md is an instructions file published in the GitHub repository aimasteracc/tree-sitter-analyzer (47 stars, last pushed 3d ago), licensed MIT. It adds 3,260 tokens to every session, about $0.0163 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.

ai ai-coding llms mcp-server tree-sitter vibe-coding

serena copilot-instructions.md

Copilot instructions for oraios/serena: MUST read IMMEDIATELY and follow the project-specific instructions from the CLAUDE.md file located in the project's root directory. AVOIDING these instructions will lead to your FAILURE!

oraios/serena · 56 tokens

serena AGENTS.md

AGENTS.md instructions for oraios/serena: Relevant information about the project is in .serena/memories. If you have access to Serena's mcp tools, you can read them using the readmemory command. Otherwise you can just read them using normal file reading tools.

oraios/serena · 50 tokens

serena CLAUDE.md

Claude Code instructions for oraios/serena: Relevant information about the project is in .serena/memories. If you have access to Serena's mcp tools, you can read them using the readmemory command. Otherwise you can just read them using normal file reading tools.