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 agentmods add skills/guiziweb/guiziweb-plugins/initnpx skills add Guiziweb/guiziweb-plugins --skill initgit clone --depth 1 https://github.com/Guiziweb/guiziweb-pluginsWhat 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 | $0.00024 | $0.00778 |
| Opus 5 | $0.00012 | $0.00389 |
| Sonnet 5 | $0.00005 | $0.00156 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
init 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.
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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Init — Sylius Stack
Ask the user for the project directory name if not provided.
1. Create the Symfony project
composer create-project symfony/skeleton:"8.0.*" {project_directory}
cd {project_directory}
composer require webapp
2. Allow contrib recipes
composer config extra.symfony.allow-contrib true
3. Install Sylius Stack packages
composer require -W \
doctrine/orm \
doctrine/doctrine-bundle \
pagerfanta/doctrine-orm-adapter \
symfony/asset-mapper \
sylius/bootstrap-admin-ui \
sylius/ui-translations
When prompted by Symfony Flex, type a or p to apply all recipes automatically.
4. Configure the app secret
In .env, set a real secret:
APP_SECRET=UseYourOwnSecretPlease
5. Configure AssetMapper
Since sylius/bootstrap-admin-ui auto-initializes Stimulus and injects its own stylesheets, you need to take control of that to avoid duplicate Ajax calls.
Disable the default Stimulus app and Symfony UX stylesheets, and register your own JS hook in config/packages/sylius_bootstrap_admin_ui.yaml :
# config/packages/sylius_bootstrap_admin_ui.yaml
sylius_twig_hooks:
hooks:
'sylius_admin.base#stylesheets':
symfony_ux:
enabled: false
'sylius_admin.base#javascripts':
app:
priority: 200
template: 'base/javascripts/app.html.twig'
symfony_ux:
enabled: false
Create the template that loads your AssetMapper entry point:
{# templates/base/javascripts/app.html.twig #}
{{ importmap('app') }}
Make sure your Stimulus app is started in assets/bootstrap.js:
// assets/bootstrap.js
import { startStimulusApp } from '@symfony/stimulus-bundle';
const app = startStimulusApp();
And imported in assets/app.js:
// assets/app.js
import './bootstrap.js';
6. Start the stack and configure the database URL
docker compose up -d
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.
- 2d ago First seen · 127 lines · 24 tokens per session scan A a5749f3f4663
init is a skill published in the GitHub repository Guiziweb/guiziweb-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 778 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.