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/jackfranklin/dotfiles/ast-grepnpx skills add jackfranklin/dotfiles --skill ast-grepgit clone --depth 1 https://github.com/jackfranklin/dotfilesWrote 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/jackfranklin/dotfiles/ast-grep)<a href="https://agentmods.dev/skills/jackfranklin/dotfiles/ast-grep"><img src="https://agentmods.dev/badge/skills/jackfranklin/dotfiles/ast-grep.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.00040 | $0.00585 |
| Opus 5 | $0.00020 | $0.00293 |
| Sonnet 5 | $0.00008 | $0.00117 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
ast-grep 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.
What it actually says
Use ast-grep (CLI binary ast-grep or sg) for structural, syntax-tree aware code search.
Decision Boundary: ast-grep vs ripgrep
-
Use
ripgrep(rg) when:- Searching for exact literal strings, comments, import paths, or single-line identifiers.
- Searching non-AST/plain text files (markdown, JSON, YAML, config files).
-
Use
ast-grepwhen:- Matching multiline code blocks, call signatures, or nested control structures.
- Searching for code pattern equivalence regardless of formatting, spacing, or line breaks.
- Filtering out false positives in comments or string literals.
- Searching for functions called with specific argument patterns (e.g. callback functions, specific parameter types).
CLI Command Usage
Execute searches:
ast-grep run --pattern '<PATTERN>' --lang <LANG> <DIR>
Or short alias:
sg run -p '<PATTERN>' -l <LANG> <DIR>
Common Language Identifiers (-l / --lang)
ts, tsx, js, jsx, python, go, rust, cpp, c, html, css.
Pattern Syntax Cheat Sheet
| Syntax | Description | Example |
|---|---|---|
$VAR |
Single AST node variable | foo($A, $B) |
$$$ARGS |
Zero or more AST nodes (spread metavariable) | console.log($$$ARGS) |
___ |
Wildcard single node (anonymous) | if (___) { $$$ } |
Syntax Examples
-
Find all function calls with callback as last argument:
ast-grep run -p '$FUNC($$$ARGS, ($$$PARAMS) => { $$$BODY })' -l ts . -
Find specific JSX/TSX element usage:
ast-grep run -p '<Button onClick={$HANDLER}>$$$CHILDREN</Button>' -l tsx . -
Find error logging calls:
ast-grep run -p 'logger.error($$$ARGS)' -l ts src/ -
Find async functions without try-catch:
ast-grep run -p 'async function $NAME($$$ARGS) { $$$BODY }' -l ts src/
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 · 66 lines · 40 tokens per session scan A 10478e8a685d
ast-grep is a skill published in the GitHub repository jackfranklin/dotfiles (254 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 585 once invoked, about $0.0002 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…