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 skills/sshadows/tree-sitter-al/al-file-validationnpx skills add SShadowS/tree-sitter-al --skill al-file-validationgit clone --depth 1 https://github.com/SShadowS/tree-sitter-alWrote 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/skills/sshadows/tree-sitter-al/al-file-validation)<a href="https://agentmods.dev/skills/sshadows/tree-sitter-al/al-file-validation"><img src="https://agentmods.dev/badge/skills/sshadows/tree-sitter-al/al-file-validation.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.00088 | $0.02384 |
| Opus 5 | $0.00044 | $0.01192 |
| Sonnet 5 | $0.00018 | $0.00477 |
| Haiku 4.5 | $0.00009 | $0.00238 |
Grade A, and why
AL File Total Validation 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 4d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AL File Total Validation
tree-sitter parse file.al answering "no errors" says almost nothing. Every
defect found in 4.0.0 — 574,694 dropped bytes, three inverted precedence
levels, two node types shipping two shapes each, an omitted list separator
silently absorbed as an extra element — produced a clean error count. An
error count can only see what the parser noticed going wrong. It cannot see
what the parser lexed and threw away, or attached to the wrong parent, or
grouped the wrong way round.
This skill answers the two questions that actually matter, separately:
| question | fails when | |
|---|---|---|
| Completeness | does everything in the source reach the tree? | a token is lexed and dropped; a construct produces no node; a node is unreachable by any query |
| Soundness | is everything the tree claims true of the source? | a required field is empty; a captured span disagrees with the file |
Run it
./tools/ts-lock.sh python tools/validate_al_file.py path/to/File.al
./tools/ts-lock.sh python tools/validate_al_file.py path/to/File.al --json
./tools/ts-lock.sh python tools/validate_al_file.py --self-test
Wrap in tools/ts-lock.sh — it builds the shared al.dll that every worktree
of this repo shares by grammar name, and a concurrent build corrupts it
without either run erroring.
Exit 0 all gating checks passed · 1 a gating check failed · 2 could not
run. --strict-reachability promotes the reachability NOTE to a gating check.
The seven checks
Each is written so it CAN fail, and --self-test proves each one does by
breaking something on purpose and requiring the right check — not merely
some check — to report it.
-
parse-integrity — ERROR and MISSING nodes with positions. Deliberately first and deliberately the weakest: it is the check every other tool in the repo already performs, and it is the one that missed every 4.0.0 defect.
-
byte-roundtrip (completeness) — reconstructs the file from its leaf nodes and the gaps between them, and requires the result to be byte-identical to the source. A gap holding anything but whitespace is a byte the parser lexed and dropped. This is the check that would have caught the 574,694, and no error count can substitute for it, because a dropped token leaves no ERROR behind.
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.
- 4d ago First seen · 189 lines · 88 tokens per session scan A 66cd5351563b
AL File Total Validation is a skill published in the GitHub repository SShadowS/tree-sitter-al (24 stars, last pushed 23d ago), licensed MIT. It adds 88 tokens to every session and 2,384 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…