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/extends-gridnpx skills add Guiziweb/guiziweb-plugins --skill extends-gridgit 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/extends-grid)<a href="https://agentmods.dev/skills/guiziweb/guiziweb-plugins/extends-grid"><img src="https://agentmods.dev/badge/skills/guiziweb/guiziweb-plugins/extends-grid.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 | $0.00023 | $0.01294 |
| Opus 5 | $0.00012 | $0.00647 |
| Sonnet 5 | $0.00005 | $0.00259 |
| Haiku 4.5 | $0.00002 | $0.00129 |
Grade A, and why
extends-grid 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 4d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Extend an existing Sylius Grid
Customize a Sylius core grid (e.g. sylius_admin_product, sylius_admin_customer, sylius_admin_product_review) without replacing it. Sylius merges the override on top of the inherited definition — only declare the keys you change.
Not for new grids — use /sylius-app:add-grid instead.
1. Identify the target grid
Ask the user for the grid alias if not provided. Inspect the current definition:
bin/console sylius:debug:grid {alias}
Run without an argument to get an interactive list of all registered grids — useful when the exact alias is unknown.
Read the output before writing: override keys must exactly match existing field/filter/action names. Setting enabled: false on a key that does not exist is a silent no-op.
2. Write the override
File location matches the rest of the project: config/packages/grids/{alias}.yaml (e.g. sylius_admin_product.yaml). Naming the file after the alias keeps overrides self-documenting.
Assumes config/packages/_sylius.yaml already imports grids/*.yaml at its top. If not, run /sylius-app:add-grid once to scaffold it.
Only include the keys being modified — everything else stays inherited.
Hide a field / filter / action
sylius_grid:
grids:
sylius_admin_product_review:
fields:
title:
enabled: false
filters:
title:
enabled: false
actions:
item:
delete:
enabled: false
Reorder fields
position: N controls display order (lower = earlier). Declare it on the fields to reorder.
sylius_grid:
grids:
sylius_admin_product_review:
fields:
status:
position: 1
rating:
position: 2
author:
position: 3
Change a label
sylius_grid:
grids:
sylius_admin_product_review:
fields:
date:
label: app.ui.product_review.date
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.
- 4d ago First seen · 183 lines · 23 tokens per session scan A 393b7fd730fc
extends-grid is a skill published in the GitHub repository Guiziweb/guiziweb-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 1,294 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…