fs-claude-plugin

Install

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.

Security

Grade A, and why

fs-claude-plugin 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 2d 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.

.claude-plugin/marketplace.json · 25 lines

What it actually says

{
  "name": "fs-claude-plugin",
  "owner": {
    "name": "FacturaScripts",
    "url": "https://facturascripts.com"
  },
  "plugins": [
    {
      "name": "fs-dev",
      "source": "./fs-dev",
      "description": "Plugin para programadores: skills, agentes y documentación técnica de FacturaScripts."
    },
    {
      "name": "fs-user",
      "source": "./fs-user",
      "description": "Plugin para usuarios del ERP: informes, análisis de datos y asistencia en el uso de FacturaScripts."
    },
    {
      "name": "fs-mcp",
      "source": "./fs-mcp",
      "description": "Servidor MCP de FacturaScripts: conecta Claude a una o varias instalaciones del ERP para obtener datos en tiempo real."
    }
  ]
}

Changes

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.

Related

Other plugins, from other repositories