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/QuentinEnhancementStudio/wix-mcp-skillWrote 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/commands/quentinenhancementstudio/wix-mcp-skill/update-wix-recipes)<a href="https://agentmods.dev/commands/quentinenhancementstudio/wix-mcp-skill/update-wix-recipes"><img src="https://agentmods.dev/badge/commands/quentinenhancementstudio/wix-mcp-skill/update-wix-recipes/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/commands/quentinenhancementstudio/wix-mcp-skill/update-wix-recipes"><img src="https://agentmods.dev/badge/commands/quentinenhancementstudio/wix-mcp-skill/update-wix-recipes.svg" alt="Reviewed on agentmods" width="80" 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.00015 | $0.00453 |
| Opus 5.5 | $0.00006 | $0.00181 |
| Sonnet 5.5 | $0.00003 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
update-wix-recipes 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 2mo 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.
What it actually says
Update the Wix MCP skill recipe files with current data from the Wix MCP.
Steps
-
Call
WixREADME()to get the current recipe index from Wix. -
Parse the response and extract each domain section (Bookings, Stores, Payments, Restaurants, Blog, Pricing Plans, Contacts, CMS, Sites, Events, Platform, Media, Rich Content).
-
For each domain, compare the recipes in the WixREADME response with the existing file at
~/.claude/skills/wix-mcp/recipes/<domain>.md. Domain-to-filename mapping:- Bookings -> recipes/bookings.md
- Stores -> recipes/stores.md
- Payments -> recipes/payments.md
- Restaurants -> recipes/restaurants.md
- Blog -> recipes/blog.md
- Pricing Plans -> recipes/pricing-plans.md
- Contacts -> recipes/contacts.md
- CMS -> recipes/cms.md
- Sites -> recipes/sites.md
- Events -> recipes/events.md
- Platform -> recipes/platform.md
- Media -> recipes/media.md
- Rich Content -> recipes/rich-content.md
-
For each file that differs or is missing, update it using this format:
# <Domain> Recipes | Recipe | Keywords | URL | |--------|----------|-----| | <Recipe Name> | <keyword1>, <keyword2>, ... | `<article URL>` |Generate 3-5 relevant keywords per recipe based on its name and description.
-
If WixREADME returns recipes for a domain that has no file, create the new file and add a corresponding entry to
domain-routing.md. -
Report a summary to the user:
- Which files were updated (and what changed)
- Which files were already up-to-date
- Any new domains added
- Total recipe count before and after
-
Log the update:
~/.claude/skills/wix-mcp/scripts/log.sh UPDATE recipes "<summary>"
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.
- 2mo ago First seen · 55 lines · 15 tokens per session scan A dfb1f65e6bb2
update-wix-recipes is a command published in the GitHub repository QuentinEnhancementStudio/wix-mcp-skill (2 stars, last pushed 8mo ago), licensed MIT. It adds 15 tokens to every session and 453 once invoked, about $0.0001 per session on Opus 5.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.
update-wix-recipes compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| update-wix-recipesQuentinEnhancementStudio/wix-mcp-skill | Command | 2 | 8mo ago | MIT | A | 15 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | today | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | today | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | today | MIT | A | 13 | Claude Code |
| convergegithub/spec-kit | Command | 148k | today | MIT | A | 35 | Claude Code |
| speckit.bug.testgithub/spec-kit | Command | 148k | today | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | today | MIT | A | 26 | Claude Code |