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 yailPeralta/ast-mcp-server --skill structural-code-editinggit clone --depth 1 https://github.com/yailPeralta/ast-mcp-serverWrote 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/yailperalta/ast-mcp-server/structural-code-editing)<a href="https://agentmods.dev/skills/yailperalta/ast-mcp-server/structural-code-editing"><img src="https://agentmods.dev/badge/skills/yailperalta/ast-mcp-server/structural-code-editing/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/yailperalta/ast-mcp-server/structural-code-editing"><img src="https://agentmods.dev/badge/skills/yailperalta/ast-mcp-server/structural-code-editing.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00037 | $0.01222 |
| Opus 5.5 | $0.00015 | $0.00489 |
| Sonnet 5.5 | $0.00007 | $0.00244 |
| Haiku 4.5 | $0.00004 | $0.00122 |
Grade A, and why
structural-code-editing 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 1mo 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Edición estructural con el servidor MCP ast
Activation Contract
Cargar este skill antes de navegar semánticamente, analizar impacto o referencias, consultar diagnostics o preparar una mutación TypeScript/JavaScript gobernada por el compilador.
No forzar un roundtrip AST para Markdown, configuración, comentarios ni una edición textual trivial en un archivo ya conocido. Si las tools ast_* no están disponibles, declarar el fallback y no presentar búsquedas textuales como evidencia compiler-backed.
Published v0.12.0 requires Node.js >=22.13.0 and retains immutable release evidence from exact Node.js 22.13.0 plus the governed Node.js 24 line.
Hard Rules
- Verificar primero que las tools existen y que
ast_get_project_statusinforma un proyecto usable. - Tratar como autoritativa solo evidencia
compiler+exact+resolved+fresh. - Revisar siempre límites,
completeness,unresolvedytruncationantes de inferir ausencia. - Preparar mutaciones, revisar preview y diagnostics, y aplicar únicamente con el
operation_idyplan_hashexactos. - Nunca reconstruir postimages desde un diff; después del apply, ejecutar el gate canónico del proyecto.
- Conservar
correlation_iden errores públicos sin exponer source, paths absolutos, argumentos, environment, cache, stacks ni credenciales.
Impacto y candidatos de test
ast_get_impact separa dos canales. coverage asigna a cada kind/direction/endpoint una de not_applicable, completed, unsupported o unfinished; truncation y work describen límites de recorrido. incomplete es true si falla cualquiera. proven_empty exige cero edges, cobertura aplicable completa y ningún límite agotado.
La selección default conserva los siete kinds. contains aplicable es unsupported, por lo que el default puede ser semánticamente incompleto sin truncamiento. Calls directas por identificador, new y tagged templates pueden ser exactas; property, element, dynamic, unresolved, multiple o external dispatch no generan edges adivinados y dejan esa dirección unfinished. No presentar esto como certificación de #219 o #220.
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.
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.
- 1mo ago Changed · +8 lines 33d0c6520c1e
- 1mo ago First seen · 68 lines · 37 tokens per session scan A df2ebc3f3903
structural-code-editing is a skill published in the GitHub repository yailPeralta/ast-mcp-server (4 stars, last pushed yesterday), licensed ISC. It adds 37 tokens to every session and 1,222 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
create-gsd-extension
Create, debug, and iterate on GSD extensions (TypeScript modules adding tools, commands, event hooks, custom UI, and providers). Use when asked to build an extension, add a tool the LLM can call, register a slash command, hook into GSD events, create custom TUI components, or modify GSD behavior. Triggers on…
drizzle-orm-expert
Expert in Drizzle ORM for TypeScript — schema design, relational queries, migrations, serverless DB integration. Use when building type-safe database layers with Drizzle, migrating from Prisma, or optimizing edge runtime DB access.
bun
Master the Bun all-in-one toolkit — runtime, package manager, test runner, and bundler. Use when writing, running, testing, or bundling TypeScript/JavaScript with Bun. Triggers on "bun", "bunx", "bun install", "bun test", "bun run". If the user asks to 'write tests' without specifying the type, you MUST ask 'Unit…
drizzle-orm
Drizzle ORM best practices. Use when configuring databases, designing schemas, writing queries, or handling migrations with Drizzle ORM, particularly with Cloudflare D1 or SQLite. NOT for database setup without an explicit engine. Require engine specification (Postgres/MySQL/SQLite). Use for ORM-managed migrations.
hono
Hono framework best practices. Use when building, reviewing, or debugging Hono applications, especially on Cloudflare Workers. Covers routing, middleware, context (c), and RPC patterns. Do NOT trigger for generic 'build a server' requests unless Hono or Cloudflare Workers is explicitly requested.
zod
Zod schema validation standards. Use when defining schemas, parsing user input, transforming data, or integrating type-safe boundaries in API endpoints and configurations. SECURITY: Zod schemas are your primary security boundary. Ensure they are strict and handle all edge cases.