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.
git clone --depth 1 https://github.com/Guiziweb/guiziweb-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/guiziweb/guiziweb-plugins/marketplace)<a href="https://agentmods.dev/plugins/guiziweb/guiziweb-plugins/marketplace"><img src="https://agentmods.dev/badge/plugins/guiziweb/guiziweb-plugins/marketplace/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/plugins/guiziweb/guiziweb-plugins/marketplace"><img src="https://agentmods.dev/badge/plugins/guiziweb/guiziweb-plugins/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
guiziweb-plugins marketplace 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "guiziweb-plugins",
"owner": {
"name": "Guiziweb",
"email": "[email protected]"
},
"metadata": {
"description": "Sylius plugin development tools for Claude Code",
"pluginRoot": "./plugins"
},
"plugins": [
{
"name": "sylius-plugin",
"source": "./plugins/sylius-plugin",
"description": "Skills for developing a Sylius plugin (PluginSkeleton, test application, distributable package)",
"author": {
"name": "Guiziweb",
"email": "[email protected]"
},
"homepage": "https://github.com/Guiziweb/guiziweb-plugins",
"repository": "https://github.com/Guiziweb/guiziweb-plugins",
"license": "MIT",
"keywords": [
"sylius",
"plugin"
],
"category": "productivity"
},
{
"name": "sylius-app",
"source": "./plugins/sylius-app",
"description": "Skills for integrating in a Sylius application (extend core entities, add custom resources)",
"author": {
"name": "Guiziweb",
"email": "[email protected]"
},
"homepage": "https://github.com/Guiziweb/guiziweb-plugins",
"repository": "https://github.com/Guiziweb/guiziweb-plugins",
"license": "MIT",
"keywords": [
"sylius",
"app"
],
"category": "productivity"
},
{
"name": "sylius-stack",
"source": "./plugins/sylius-stack",
"description": "Build Symfony apps with the Sylius Stack (Resource, Grid, Bootstrap Admin UI, Twig Hooks)",
"author": {
"name": "Guiziweb",
"email": "[email protected]"
},
"homepage": "https://github.com/Guiziweb/guiziweb-plugins",
"repository": "https://github.com/Guiziweb/guiziweb-plugins",
"license": "MIT",
"keywords": [
"sylius",
"stack"
],
"category": "productivity"
},
{
"name": "claude-hud",
"source": {
"source": "github",
"repo": "Guiziweb/claude-The plugins it lists here
This marketplace lists 3 plugins kept in the same repository. Each has its own page, its own measurements and its own install command.
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 First seen · 86 lines scan A 4744061aa631
guiziweb-plugins marketplace is a plugin published in the GitHub repository Guiziweb/guiziweb-plugins (4 stars, last pushed 2mo 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
shopify-plugin
Shopify developer tools for Claude Code — search Shopify docs, generate and validate GraphQL, Liquid, and UI extension code. Skill scripts send usage telemetry (queries, code, model/client identifiers) to shopify.dev by default; set OPTOUTINSTRUMENTATION=true, or create an empty file at /.config/shopify-ai-toolkit/o.
b2c-cli
B2C CLI Skills for Salesforce Commerce Cloud development.
sap-mm
Procurement, inventory, GR/IR, invoice verification.
product-sales-analysis
Analyzes sales/ecommerce CSV data and generates an interactive HTML dashboard with KPIs, category performance, YoY growth trends, marketing ROI and prioritized recommendations.
jpm-payments-skills
Conversational agent skills that walk a merchant from J.P. Morgan Payments onboarding through a working API integration. Supports Checkout and Online Payments in the initial release. Generates language-specific OAuth modules (Node/TypeScript, Python, Java idiomatic; other languages via canonical algorithm).
shopify-app-builder
Production-focused Shopify app engineering guidance for Gemini CLI.