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.
/plugin marketplace add and3r817/dot-claude-pluginsnpx agentmods add plugins/and3r817/dot-claude-plugins/ast-grepgit clone --depth 1 https://github.com/and3r817/dot-claude-pluginsWrote 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/plugins/and3r817/dot-claude-plugins/ast-grep)<a href="https://agentmods.dev/plugins/and3r817/dot-claude-plugins/ast-grep"><img src="https://agentmods.dev/badge/plugins/and3r817/dot-claude-plugins/ast-grep.svg" alt="Measured on agentmods" height="20"></a>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 3d 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
{
"name": "ast-grep",
"version": "2.1.1",
"description": "Structural code search using AST patterns. Translates natural language queries into ast-grep rules for precise code matching beyond text search.",
"author": {
"name": "and3r817",
"url": "https://github.com/and3r817"
},
"homepage": "https://github.com/and3r817/dot-claude-plugins/tree/main/ast-grep#readme",
"repository": "https://github.com/and3r817/dot-claude-plugins",
"license": "MIT",
"keywords": [
"ast-grep",
"ast",
"code-search",
"structural-search",
"pattern-matching",
"refactoring"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 75 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 3d ago First seen · 21 lines scan A 26b3fa63b53f
ast-grep is a plugin published in the GitHub repository and3r817/dot-claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-31.
Other plugins, from other repositories
qte77-claude-code-plugins marketplace
Plugin marketplace listing 27 plugins: python-dev, commit-helper, codebase-tools, cpp-desktop, cc-meta.
cc-meta
Claude Code meta-skills for cross-project synthesis, context compaction, session intelligence, and memory seed template.
codebase-tools
Isolated codebase research, quality hardening, and build error resolution via skills and agents.
docs-generator
Document generation for writeups, tech specs (ADR/RFC/design docs), and reports with optional pandoc PDF export.
makefile-core
Skills and linting for consistent, rigorous Makefiles across projects — auto-detects project type, extensible via scaffold-.md references.
market-research
GTM market research pipeline with teams mode parallel dispatch and configurable 2x2 strategy matrix.