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/wake-engineering/ai-plugin/wake-hotsite-bannersnpx skills add wake-engineering/ai-plugin --skill wake-hotsite-bannersgit clone --depth 1 https://github.com/wake-engineering/ai-pluginWrote 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/wake-engineering/ai-plugin/wake-hotsite-banners)<a href="https://agentmods.dev/skills/wake-engineering/ai-plugin/wake-hotsite-banners"><img src="https://agentmods.dev/badge/skills/wake-engineering/ai-plugin/wake-hotsite-banners.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.00047 | $0.00796 |
| Opus 5 | $0.00023 | $0.00398 |
| Sonnet 5 | $0.00009 | $0.00159 |
| Haiku 4.5 | $0.00005 | $0.00080 |
Grade A, and why
wake-hotsite-banners 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 5d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wake Hotsite Banners
Forbidden: api.fbits.net (and any *.fbits.net). Canonical source: https://wakecommerce.readme.io/docs/schema
Hotsite (landing page) guidance for Wake Commerce storefront integrations. This skill covers banners, contents, products, and SEO for promotional and campaign pages.
When to use
- Building landing pages from hotsite URL routes
- Implementing promotional or campaign pages
- Rendering banner/carousel sections from API data
- Mapping content blocks and related products
- Applying SEO metadata from hotsite payload
Workflow steps
- Resolve the incoming route to a hotsite
urlvalue. - Call
hotsite(url, partnerAccessToken)with the appropriate context. - Map response data to page sections:
banners,contents,productsByOffset,seo. - Apply SEO fields to the document head.
- Validate fallback behavior when URL is invalid or API is unavailable.
hotsite(url, partnerAccessToken)
Use the hotsite root query to fetch landing page data.
- url: Landing page path (example:
/promo/black-friday). - partnerAccessToken: Optional in standard storefront contexts; required in partner/wholesale scenarios.
- Security note: Never hardcode
partnerAccessToken. Source it from secure server-side configuration or environment-managed flows.
query Hotsite($url: String!, $partnerAccessToken: String) {
hotsite(url: $url, partnerAccessToken: $partnerAccessToken) {
url
banners {
id
name
images {
url
}
links {
url
}
}
contents {
id
title
type
}
productsByOffset(limit: 20, offset: 0) {
productId
productName
alias
images {
url
}
prices {
listPrice
price
}
}
seo {
content
name
type
httpEquiv
scheme
}
}
}
Fields to map
| Field | Purpose |
|---|---|
banners |
Banner/carousel rendering content |
contents |
Page sections and content blocks |
productsByOffset |
Product listing area for the landing page |
seo |
Meta tags and head metadata |
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.
- 5d ago First seen · 105 lines · 47 tokens per session scan A 5d2baf989b93
wake-hotsite-banners is a skill published in the GitHub repository wake-engineering/ai-plugin (2 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 796 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…