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 depurar-y-testeargit 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/depurar-y-testear)<a href="https://agentmods.dev/skills/facturascripts/fs-claude-plugin/depurar-y-testear"><img src="https://agentmods.dev/badge/skills/facturascripts/fs-claude-plugin/depurar-y-testear/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/depurar-y-testear"><img src="https://agentmods.dev/badge/skills/facturascripts/fs-claude-plugin/depurar-y-testear.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.00030 | $0.00752 |
| Opus 5 | $0.00015 | $0.00376 |
| Sonnet 5 | $0.00006 | $0.00150 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
depurar-y-testear 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 10d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Depurar y Testear en FacturaScripts
Activar el modo debug
Editar config.php en la raíz de FacturaScripts:
define('FS_DEBUG', true);
Esto activa la barra de debug en la parte inferior derecha con información de queries, logs y errores.
Mostrar mensajes y errores
use FacturaScripts\Core\Tools;
// Info (mensaje informativo)
Tools::log()->info('Mensaje informativo');
// Warning
Tools::log()->warning('Atención: algo no está bien');
// Error
Tools::log()->error('Ha ocurrido un error');
// Error con traducción
Tools::log()->error('campo-obligatorio', ['%field%' => 'Nombre']);
// Mostrar en la interfaz (toast)
Tools::log('audit')->info('Acción completada');
Ver logs
Los logs se almacenan en la tabla logmessages y se pueden ver desde Administrador → Log.
Reconstruir Dinamic
Cuando los cambios no se reflejan, hacer clic en Administrador → Plugins → Reconstruir o activar/desactivar el plugin.
Tests unitarios con PHPUnit
Atajo con fsmaker
Para generar el archivo de test base y ejecutarlos, usa:
# Crear un nuevo test
fsmaker test
# Ejecutar todos los tests del proyecto
fsmaker run-tests
Archivo: Test/MiPluginTest.php
<?php
namespace FacturaScripts\Test\Plugins;
use FacturaScripts\Plugins\MiPlugin\Model\NombreModelo;
use PHPUnit\Framework\TestCase;
final class NombreModeloTest extends TestCase
{
public function testCrearRegistro(): void
{
$modelo = new NombreModelo();
$modelo->name = 'Test';
$this->assertTrue($modelo->save());
$this->assertNotEmpty($modelo->id);
// Limpiar
$this->assertTrue($modelo->delete());
}
public function testValidacion(): void
{
$modelo = new NombreModelo();
$modelo->name = ''; // Inválido
$this->assertFalse($modelo->save());
}
}
Ejecutar los tests:
composer test
# O directamente:
vendor/bin/phpunit
Verificar estilo de código
# Verificar
composer cs-check
# Corregir automáticamente
composer cs-fix
# Análisis estático
composer phpstan
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.
- 10d ago First seen · 128 lines · 30 tokens per session scan A 0087a2362601
depurar-y-testear is a skill published in the GitHub repository FacturaScripts/fs-claude-plugin (8 stars, last pushed 8d ago), licensed MIT. It adds 30 tokens to every session and 752 once invoked, about $0.0002 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-31.
Other skills, from other repositories
testing
Skill validation framework PLUS daily test-suite health and regression intelligence. Validates skill conformance (frontmatter, manifest coverage, resolver coverage). Runs the project test suite in tiered phases (unit / evals / integration / system health), classifies failures, and produces a regression-aware report.
verify
Verify that a change really works before you claim completion.
detect-static-dependencies
ACTIVATION PREREQUISITE: the request or discovered target must explicitly identify C#, .NET, .cs, or .csproj; otherwise stay dormant without invoking this skill. USE FOR: locating System.DateTime.Now/UtcNow, System.IO.File/Directory, System.Environment, HttpClient, Console, or Process usage in C#; auditing C# code for…
working-effectively-with-legacy-code
Apply Michael Feathers-inspired legacy-code rules when changing hard-to-test code safely with characterization tests, seams, sprout methods, or wrap methods.
refactoring-guru
Apply Refactoring.Guru-inspired rules when diagnosing code smells, choosing refactoring techniques, and stopping cleanup before uncontrolled redesign.
refactoring
Apply Martin Fowler-inspired refactoring rules when improving existing code structure while preserving observable behavior.