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 FacturaScripts/fs-claude-plugin --skill skill-pull-requestgit clone --depth 1 https://github.com/FacturaScripts/fs-claude-pluginWrote 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/facturascripts/fs-claude-plugin/skill-pull-request)<a href="https://agentmods.dev/skills/facturascripts/fs-claude-plugin/skill-pull-request"><img src="https://agentmods.dev/badge/skills/facturascripts/fs-claude-plugin/skill-pull-request/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/facturascripts/fs-claude-plugin/skill-pull-request"><img src="https://agentmods.dev/badge/skills/facturascripts/fs-claude-plugin/skill-pull-request.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.00034 | $0.01229 |
| Opus 5.5 | $0.00014 | $0.00492 |
| Sonnet 5.5 | $0.00007 | $0.00246 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade A, and why
skill-pull-request 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Requests y Ramas — Buenas Prácticas
Un buen pull request cuenta una historia: qué problema resuelve, cómo lo resuelve y cómo se puede verificar. El objetivo es que el revisor entienda el contexto sin tener que adivinar, y que el historial del proyecto quede limpio y rastreable.
Creación de ramas
La convención de nombres de rama ayuda a identificar de un vistazo de qué trata cada rama y a vincularla con su tarea correspondiente.
Convención de nombres
Si el usuario proporciona un número de tarea (por ejemplo, 4544), el nombre de la rama debe comenzar con ese número seguido de una descripción corta en kebab-case:
<número-tarea>-<descripción-corta>
Ejemplos:
- Tarea 4544 sobre descuentos →
4544-descuento-pronto-pago - Tarea 3821 sobre informes →
3821-informe-trimestral-iva - Tarea 5102 sobre API →
5102-endpoint-clientes
Si no hay número de tarea, usa solo la descripción descriptiva:
fix-calculo-iva-facturas
feat-exportar-csv-clientes
refactor-modelo-presupuestos
Flujo al crear la rama
- Asegúrate de estar en la rama base actualizada (
mainomaster):git checkout main && git pull - Crea la nueva rama:
git checkout -b <nombre-rama> - Si el usuario dio un número de tarea, confirma el nombre propuesto antes de crearla
Estructura del Pull Request
Usa gh pr create con esta estructura:
gh pr create --title "<título>" --body "$(cat <<'EOF'
## Descripción
<Explicación clara de qué hace esta PR y por qué>
## Tarea relacionada
<Enlace a la tarea si hay número>
## Cambios realizados
<Lista breve de los cambios principales>
## Cómo probar
<Pasos para verificar que funciona correctamente>
EOF
)"
No añadas firmas, marcas del asistente ni líneas Co-Authored-By salvo que el usuario las solicite expresamente.
Título de la PR
El título debe ser conciso (menos de 70 caracteres) y describir el cambio principal. Escríbelo en español y en imperativo, igual que los commits:
Ejemplos:
- "Añadir descuento por pronto pago en facturas"
- "Corregir cálculo de IVA en informe trimestral"
- "Refactorizar modelo de presupuestos"
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 · -96 tokens per session 8aa760db140c
- 1mo ago First seen · 125 lines · 130 tokens per session scan A 1b0cf84fe1bc
skill-pull-request is a skill published in the GitHub repository FacturaScripts/fs-claude-plugin (10 stars, last pushed 10d ago), licensed MIT. It adds 34 tokens to every session and 1,229 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…