tree-sitter-analyzer

tree-sitter-analyzer is a skill for Codex from plurigrid/asi. It costs 0 tokens per session (2,411 once invoked), scanned A, original, MIT.

A code-structure analyzer that parses source files into a syntax tree, the hierarchical representation of code. It extracts modules and dependencies for verification and theorem mapping, with support for Julia and planned Lean4 extension.

In plain words
What is it for?
Use it to analyze Julia modules, build dependency graphs, verify integrations, and map code structures to formal theorems.
Why use it?
It reduces the effort and missed connections involved in manually checking imports, modules, and dependency graphs.

Skill for Codex

Written for Codex: installed under .codex/.

Good fit Use it to analyze Julia modules, build dependency graphs, verify integrations, and map code structures to formal theorems.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/plurigrid/asi/tree-sitter-analyzer
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.

Any agent
npx skills add plurigrid/asi --skill tree-sitter-analyzer
Clone the repo
git clone --depth 1 https://github.com/plurigrid/asi

Made for: Codex.

Wrote 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.

agentmods badge for tree-sitter-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/skills/plurigrid/asi/tree-sitter-analyzer/github.svg)](https://agentmods.dev/skills/plurigrid/asi/tree-sitter-analyzer)
Your own site
<a href="https://agentmods.dev/skills/plurigrid/asi/tree-sitter-analyzer"><img src="https://agentmods.dev/badge/skills/plurigrid/asi/tree-sitter-analyzer/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.

agentmods 80×15 button for tree-sitter-analyzer

Your own site · 80×15
<a href="https://agentmods.dev/skills/plurigrid/asi/tree-sitter-analyzer"><img src="https://agentmods.dev/badge/skills/plurigrid/asi/tree-sitter-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,411 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02411
Opus 5 $0.00000 $0.01205
Sonnet 5 $0.00000 $0.00482
Haiku 4.5 $0.00000 $0.00241

Measured 8d ago against content hash 8ef58666167b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

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

ies/music-topos/.codex/skills/tree-sitter-analyzer/SKILL.md · 382 lines

How it starts

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

Tree-Sitter Analyzer Skill

Version: 1.0.0 Status: Production Ready Date: December 22, 2025 Phase: 2 Stage 3 Foundation


Overview

Automated code structure analysis for module verification and cross-prover theorem mapping using tree-sitter incremental parsing. Enables 100x+ speedup on integration verification tasks compared to manual analysis.

Quick Stats:

  • 550+ lines of code (2 modules)
  • 350+ lines of tests (10 test cases, 10/10 PASS)
  • <1ms per operation (well under 200ms target)
  • Zero external dependencies
  • Full Julia language support
  • Ready for Lean4 extension

Problem Statement

Current Workflow (Manual Analysis):

  • Agent integration verification: 5-40 minutes per task
  • Function extraction: 1-5 minutes per module
  • Dependency analysis: 5-10 minutes per graph
  • Error rate: 5-10% (missed imports, false positives)
  • Scalability: ❌ Not practical for 100+ modules

With Tree-Sitter Analyzer:

  • Module analysis: <1ms
  • Dependency graphs: <1ms
  • Integration verification: <5ms
  • Error rate: 0% (AST-based, proven correct)
  • Scalability: ✅ 1,000+ modules possible

Capabilities

Core Functions

Module Analysis:

analyze_module(path::String) -> ModuleAnalysis

Extract all symbols, dependencies, and structure from a Julia module.

Symbol Extraction:

extract_functions(content::String, path::String) -> Vector{FunctionSignature}
extract_structs(content::String, path::String) -> Vector{StructDefinition}
extract_exports(content::String, path::String) -> Vector{Symbol}
extract_imports(content::String, path::String) -> Vector{Symbol}

Julia-Specific Analysis:

extract_docstrings(content::String) -> Vector{DocstringInfo}
extract_type_annotations(content::String) -> Dict{String, String}
find_macros(content::String) -> Vector{MacroUsage}
analyze_module_structure(path::String) -> JuliaModule

Dependency Analysis:

build_dependency_graph(root::String) -> DependencyGraph
find_circular_dependencies(graph::DependencyGraph) -> Vector{Vector{String}}
find_integration_points(graph, from, to) -> Vector{Tuple{String, String}}

Read the full file on GitHub · 382 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. 8d ago First seen · 382 lines · 0 tokens per session scan A 8ef58666167b

Subscribe to this mod's changes

tree-sitter-analyzer is a skill published in the GitHub repository plurigrid/asi (64 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,411 tokens. 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-09-03.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens