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 Guiziweb/guiziweb-plugins --skill add-providergit 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/skills/guiziweb/guiziweb-plugins/add-provider)<a href="https://agentmods.dev/skills/guiziweb/guiziweb-plugins/add-provider"><img src="https://agentmods.dev/badge/skills/guiziweb/guiziweb-plugins/add-provider.svg" alt="Measured on agentmods" 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.00032 | $0.00715 |
| Opus 5 | $0.00016 | $0.00358 |
| Sonnet 5 | $0.00006 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
add-provider 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 8d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a Custom Provider — Sylius Stack
Ask the user if not provided:
- The resource (
ModelName) and the target operation (Index,Show,Update, etc.) - The provider class name. Default:
{ModelName}{Operation}Provider(e.g.BookShowProvider). - The namespace / path. Default:
src/Provider/(namespaceApp\Provider). For a DDD layout, ask for the infrastructure path (e.g.src/BoardGameBlog/Infrastructure/Sylius/State/Provider/).
If the user only needs a different repository method, do not create a provider — suggest the operation flags instead:
new Show(
repositoryMethod: 'findOneBySlug',
repositoryArguments: ['slug' => "request.attributes.get('slug')"],
)
1. Create the provider class
src/Provider/{ProviderName}.php
<?php
declare(strict_types=1);
namespace App\Provider;
use Sylius\Resource\Context\Context;
use Sylius\Resource\Context\Option\RequestOption;
use Sylius\Resource\Metadata\Operation;
use Sylius\Resource\State\ProviderInterface;
use Webmozart\Assert\Assert;
final class {ProviderName} implements ProviderInterface
{
public function __construct(
// TODO: inject the dependencies you need (QueryBus, HttpClient, Repository…)
) {
}
public function provide(Operation $operation, Context $context): object|array|null
{
$request = $context->get(RequestOption::class)?->request();
Assert::notNull($request);
// TODO: build and return the resource (or a collection for Index operations)
// return null if the resource cannot be found
return null;
}
}
Adjust the constructor and the provide() body with the real lookup logic. For an Index operation, return an iterable/paginator; for item operations (Show, Update, Delete), return a single object or null.
2. Wire the provider on the operation
Edit src/Entity/{ModelName}.php — add the provider: argument on the target operation:
use App\Provider\{ProviderName};
new Show(provider: {ProviderName}::class),
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.
- 8d ago First seen · 95 lines · 32 tokens per session scan A d8ac2f4320fd
add-provider is a skill published in the GitHub repository Guiziweb/guiziweb-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 715 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
convex-billing
Add Stripe billing/payments to the Convex app via @convex-dev/stripe (checkout + webhook + gating).
cloudbase-wechat-integration
A guide for connecting CloudBase applications to WeChat services, including payments, official accounts, and user identity.
commerce-app-business-config
Manage custom business configuration in an Adobe Commerce app. Use when the user wants to add, modify, or remove merchant-configurable settings (config fields, admin config, store configuration) exposed through Commerce Admin. Creates typed config fields (text, password, email, url, tel, boolean, list) in…
baselinker-webhooks
Receive BaseLinker (Base.com) webhooks. Use when building a BaseLinker order or warehouse callback receiver, because BaseLinker is not a normal webhook source: deliveries arrive as HTTP HEAD requests with NO body, the entire payload is in the query string (observed params: orderid, state), there is NO signature…
tiktok-shop-webhooks
Receive and verify TikTok Shop webhooks. Use when setting up TikTok Shop webhook handlers, debugging Authorization-header signature verification, or handling events like ORDERSTATUSCHANGE, PACKAGEUPDATE, RECIPIENTADDRESSUPDATE, PRODUCTSTATUSCHANGE, or SELLERDEAUTHORIZATION.
gplay-purchase-verification
Server-side purchase verification for in-app products and subscriptions using Google Play Developer API. Use when implementing receipt validation in your backend.