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 chrischall/zola-mcp --skill zolagit clone --depth 1 https://github.com/chrischall/zola-mcpWrote 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/chrischall/zola-mcp/zola)<a href="https://agentmods.dev/skills/chrischall/zola-mcp/zola"><img src="https://agentmods.dev/badge/skills/chrischall/zola-mcp/zola/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/skills/chrischall/zola-mcp/zola"><img src="https://agentmods.dev/badge/skills/chrischall/zola-mcp/zola.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.00092 | $0.00626 |
| Opus 5 | $0.00046 | $0.00313 |
| Sonnet 5 | $0.00018 | $0.00125 |
| Haiku 4.5 | $0.00009 | $0.00063 |
Grade A, and why
zola 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 12d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
zola-mcp
MCP server for Zola — 31 tools for managing your entire wedding via the Zola mobile API.
Tools
Vendors
list_vendors— List all booked vendorssearch_vendors— Search vendors by name/categoryadd_vendor— Book a new vendorupdate_vendor— Update vendor detailsremove_vendor— Unbook a vendor
Budget
get_budget— Budget summary with all itemsupdate_budget_item— Update cost or note
Guests
list_guests— List all guest groups with statsadd_guest— Add a guest groupupdate_guest_address— Update mailing addressremove_guest— Remove a guest group
Seating
list_seating_charts— List chartsget_seating_chart— Chart with tables/seats/occupantslist_unseated_guests— Guests not yet seatedassign_seat— Assign guest to seat
Inquiries
list_inquiries— All vendor inquiriesget_inquiry_conversation— Full conversationmark_inquiry_read— Mark as read
Events & RSVPs
list_events— All events with RSVP countstrack_rsvps— RSVP tracking per eventupdate_event— Update event detailsset_event_guests— Bulk set which guest groups are invited to an eventinvite_guest_to_event— Invite one guest or group to an eventremove_event_invitation— Remove an event invitation for a guest or group
Registry & Gifts
get_registry— Registry items with per-item purchase state (requested vs purchased quantity,marked_fulfilled,availability,inconsistent); paged vialimit/offsetget_gift_tracker— Gifts received and thank-you statusreconcile_registry— Joins the registry against the gift tracker and reports DUPLICATE_RISK (flagged fulfilled but nothing purchased, so still buyable), UNATTRIBUTED (purchased with no order behind it), ORPHAN_ORDER and a MATCHED count
Discovery
get_wedding_dashboard— Planning overviewsearch_storefronts— Search marketplaceget_storefront— Full vendor detailslist_favorites— Saved vendors
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.
- 12d ago First seen · 58 lines · 92 tokens per session scan A 0b02cdb70bac
zola is a skill published in the GitHub repository chrischall/zola-mcp (3 stars, last pushed today), licensed MIT. It adds 92 tokens to every session and 626 once invoked, about $0.0005 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.