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/omagents/omagents/ast-grepnpx skills add omagents/omagents --skill ast-grepgit clone --depth 1 https://github.com/omagents/omagentsWrote 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/omagents/omagents/ast-grep)<a href="https://agentmods.dev/skills/omagents/omagents/ast-grep"><img src="https://agentmods.dev/badge/skills/omagents/omagents/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.00055 | $0.01099 |
| Opus 5 | $0.00028 | $0.00549 |
| Sonnet 5 | $0.00011 | $0.00220 |
| Haiku 4.5 | $0.00006 | $0.00110 |
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.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AST-Grep: Structural Code Search and Rewrite
Pattern-aware code search using the ast-grep (sg) binary. Matches code by its syntactic structure, not just text.
When to Use
- Find all calls to a specific function pattern (not just the name)
- Find all instances of a code structure (e.g., all try/catch blocks)
- Rewrite code patterns across the codebase
- When grep is too imprecise (matches in strings, comments, etc.)
Prerequisites
Check if ast-grep is installed:
sg --version 2>/dev/null || npx ast-grep --version 2>/dev/null
If not installed, fall back to grep with careful regex patterns.
Basic Usage
Search
# Find all console.log calls
sg -p 'console.log($$$)' --lang javascript
# Find all function definitions with a specific name pattern
sg -p 'def $NAME($$$):' --lang python
# Find all if statements with a single return
sg -p 'if ($COND) { return $VAL }' --lang typescript
Replace
# Preview first (ALWAYS dry-run before applying)
sg -p 'console.log($$$)' -r 'logger.info($$$)' --lang javascript
# Apply (only after verifying preview)
sg -p 'console.log($$$)' -r 'logger.info($$$)' --lang javascript --update-all
Validate Pattern
# Check if pattern is valid before searching
sg -p 'pattern' --lang python --json=compact 2>&1 | head -5
Pattern Syntax
| Token | Meaning |
|---|---|
$NAME |
Match a single AST node, bind to NAME |
$$$ |
Match zero or more AST nodes (wildcard) |
| Literal text | Must match exactly in AST structure |
Examples:
# Python: find all decorators
@$DECORATOR
def $FUNC($$$):
$$$
# TypeScript: find all arrow functions assigned to const
const $NAME = ($$$) => $BODY
# Rust: find all match arms with panic
$PAT => panic!($$$)
Language Detection
ast-grep auto-detects language from file extension. Override with --lang:
sg -p 'pattern' --lang python
sg -p 'pattern' --lang typescript
sg -p 'pattern' --lang rust
sg -p 'pattern' --lang go
What ships with it
1 file 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.
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 · 137 lines · 55 tokens per session scan A 3bc1ace41a7b
ast-grep is a skill published in the GitHub repository omagents/omagents (366 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 1,099 once invoked, about $0.0003 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…