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 skills add rcarmo/piclaw-addons --skill ast-grepgit clone --depth 1 https://github.com/rcarmo/piclaw-addonsWrote 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/rcarmo/piclaw-addons/ast-grep)<a href="https://agentmods.dev/skills/rcarmo/piclaw-addons/ast-grep"><img src="https://agentmods.dev/badge/skills/rcarmo/piclaw-addons/ast-grep/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.
<a href="https://agentmods.dev/skills/rcarmo/piclaw-addons/ast-grep"><img src="https://agentmods.dev/badge/skills/rcarmo/piclaw-addons/ast-grep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00027 | $0.00497 |
| Opus 5 | $0.00014 | $0.00249 |
| Sonnet 5 | $0.00005 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00050 |
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 9d 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
AST Grep
Use this skill when text search would be noisy or unsafe.
Tools
code_search(pattern, lang, path?, limit?)— find code by AST patterncode_rewrite(pattern, rewrite, lang, path?, dry_run?)— structural find-and-replace
Examples
console.log($MSG)— find all console.log callsvar $NAME = $VAL→const $NAME = $VAL— modernize var declarationscatch ($ERR) { }— find empty catch blocksimport $X from "lodash"— find imports from a specific module
Workflow
code_search(pattern, lang, path, limit=20)— narrow path, sample first- Inspect matches — verify pattern catches what you want
code_rewrite(pattern, rewrite, lang, path, dry_run=true)— preview changes- Review the dry run output
code_rewrite(pattern, rewrite, lang, path, dry_run=false)— apply- Read changed files, run formatting/tests
Prefer other tools when
- You need plain text, comments, or strings →
grep - You need type/symbol-aware results → LSP/symbol tools if available
Safety
- Always run
dry_run=truebefore applying any rewrite - Scope with
pathto avoid unintended matches in vendored/generated code - Supported
langvalues: typescript, javascript, tsx, jsx, python, rust, go, java, c, cpp, csharp, ruby, swift, kotlin, lua, html, css, json, yaml - After applying rewrites, read changed files and run tests/formatting before moving on
Troubleshooting
- No matches: verify
langis correct (e.g.typescriptnotts), broaden pattern - Too many matches: narrow
path, add more structure to pattern, lowerlimit - Pattern error: simplify — patterns must be valid syntax in the target language
- Wrong language:
typescript≠tsx,javascript≠jsx— run separate passes
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.
- 9d ago First seen · 44 lines · 27 tokens per session scan A 236c48cf808c
ast-grep is a skill published in the GitHub repository rcarmo/piclaw-addons (23 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 497 once invoked, about $0.0001 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
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…
adk-debug
Diagnoses misbehaving ADK agents by inspecting sessions, events, tool calls, and the exact request that reached the model. Covers the adk run CLI and the adk web dev server with its session, trace, and debug HTTP endpoints. Use when an agent returns the wrong answer, ignores a tool or swallows a tool error, hangs…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
claw-admin
Claw system administration: service management, IM connections, logs, cron, and workspace diagnostics. Use when the user asks to manage claw services, connect/disconnect IM platforms, view logs, or perform system-wide operations.
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
rubber-duck
Adversarial "rubber duck" review that turns explaining-out-loud into a hallucination check. The main session is the PRESENTER (it did the work — a design doc, investigation, or analysis — and holds the real reasoning) and reconstructs the topic to a LISTENER — a spawned subagent pinned to a DIFFERENT-vendor model that…