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/sshadows/tree-sitter-al/claude-mdgit clone --depth 1 https://github.com/SShadowS/tree-sitter-alWhat 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.06801 | $0.06801 |
| Opus 5 | $0.03401 | $0.03401 |
| Sonnet 5 | $0.01360 | $0.01360 |
| Haiku 4.5 | $0.00680 | $0.00680 |
Grade A, and why
tree-sitter-al CLAUDE.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 2d 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 — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
GOAL: A parser which parses AL code CORRECT, not just without errors. That is the first and foremost goal.
This file provides guidance to Claude Code (claude.ai/code) when working with this tree-sitter parser for the AL (Application Language) programming language used in Microsoft Dynamics 365 Business Central.
Current Status: 100% production file success rate (15,358/15,358 files), 1,583 tests passing, 0 errors
Git Commit Guidelines
Always include error count in commit messages to detect regressions:
Fix XYZ pattern
[BC.History: 7 errors, 99.95% success]
Run full parse before committing: ./parse-al-parallel.sh ./BC.History/ .
Commit all generated files together — tree-sitter generate writes src/parser.c, src/grammar.json, and src/node-types.json; all three are tracked. Stage them as a set or grammar.json silently drifts.
Quick Reference
Essential Commands:
# Validation (run before completing any task)
./validate-grammar.sh # Quick: generation, tests, orphan/duplicate detection
./validate-grammar.sh --full # Full: includes production AL file parsing
# Zero-behavior-change gate for grammar refactors (byte-identical parse trees)
# Take a FRESH baseline before you change anything, and name it for the change.
# Never verify against a snapshot you did not just take: a stale one reports a
# huge delta that has nothing to do with your edit. `.snapshots/bc` was left
# behind for two months and 15,349 of its 15,358 rows had drifted.
./tools/tree-harness.sh snapshot ./BC.History .snapshots/baseline-<change> # ~16s
./tools/tree-harness.sh verify ./BC.History .snapshots/baseline-<change> # ~11s, ~22s with a large delta
# Query-coverage harness — proves the CST is lossless and values are queryable
python -m tools.query_coverage.qc run # regression gate, exits 1 on a new cluster
python -m tools.query_coverage.qc run --all # full picture
python -m tools.query_coverage.qc accept # freeze the current state as the baseline
# Standard development cycle
tree-sitter generate # Generate parser from grammar.js
tree-sitter generate --report-states-for-rule - # Rank rules by parser-state cost
tree-sitter test # Run test suite
tree-sitter test -u # Update test expectations — see the two traps below
tree-sitter parse file.al -d > debug.log 2>&1 # Debug specific files
python parse_bug_finder.py file.al debug.log # Analyze parsing bugs
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.
- 2d ago First seen · 410 lines · 6,801 tokens per session scan A 91f39753e323
tree-sitter-al CLAUDE.md is an instructions file published in the GitHub repository SShadowS/tree-sitter-al (24 stars, last pushed 21d ago), licensed MIT. It adds 6,801 tokens to every session, about $0.0340 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.