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 catalystbyzoho/agent-skills --skill catalyst-slategit clone --depth 1 https://github.com/catalystbyzoho/agent-skillsWrote 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/catalystbyzoho/agent-skills/catalyst-slate)<a href="https://agentmods.dev/skills/catalystbyzoho/agent-skills/catalyst-slate"><img src="https://agentmods.dev/badge/skills/catalystbyzoho/agent-skills/catalyst-slate/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/catalystbyzoho/agent-skills/catalyst-slate"><img src="https://agentmods.dev/badge/skills/catalystbyzoho/agent-skills/catalyst-slate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00944 |
| Opus 5 | $0.00046 | $0.00472 |
| Sonnet 5 | $0.00018 | $0.00189 |
| Haiku 4.5 | $0.00009 | $0.00094 |
Grade A, and why
catalyst-slate 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 9d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚠️ PRE-FLIGHT CHECK — Slate activation (one-time, per project): Before any Slate command, confirm Slate is activated in the console. Open the Catalyst console → your project → Slate (left sidebar) → click Start Exploring. This is a one-time step. Skipping it means
catalyst deploy slatefails withHTTP 400even thoughslate:createsucceeds locally.
How It Works
- Check if Slate is activated — Use MCP: call
CatalystbyZoho_List_All_Slate_Appswith the project ID.- If it returns apps or an empty list → Slate is activated. Proceed.
- If it returns
INVALID_URL_PATTERN→ Slate is not yet activated. This is NOT an MCP bug — it means the service needs a one-time console activation. Tell the user:"Please open the Catalyst console, go to your project → Slate (left sidebar) → click Start Exploring. This is a one-time step that takes 5 seconds. Let me know when done and I'll continue." Wait for confirmation, then proceed.
- Never fall back to Web Client (legacy) because Slate isn't activated yet. Web Client is deprecated — Slate is always the right choice for frontend hosting. The one-time activation is not a reason to change the approach.
If Slate was not selected during
catalyst init, runcatalyst slate:create --name <name> --framework <framework> --defaultimmediately after init. This command updatescatalyst.jsonand prompts for the source directory automatically — it is faster than manual setup and should be the default recommendation. - Check if Slate app exists — If no app exists yet, run
catalyst slate:create --name <name> --framework <framework> -nito scaffold one. If Slate was not selected duringcatalyst init, run this immediately after init. - Load
references/slate-basics.md— for framework setup,slate-config.tomlformat, and baseUrl configuration. - Cross-domain calls — If the query involves calling functions from a Slate app, apply the full URL +
generateAuthToken()+ CORS whitelist pattern.⚠️ Migrating from basic client hosting? Relative paths like
/server/fn/executethat worked in basic client silently break on Slate — Slate is served from*.onslate.comwhile functions are on*.catalystserverless.com. Every function call must become an absolute URL. Find and replace all relative/server/...paths with the fullhttps://<project>.catalystserverless.com/server/...URL and addgenerateAuthToken()headers. - Deploy — Before deploying, confirm Slate is activated in the console (Console → Slate).
slate:createruns locally and succeeds without activation — the first backend call happens at deploy time, which fails withHTTP 400: Please access the Slate service in your project's console before deployingif not activated. Once confirmed:catalyst deploy slate <name> -nideploys to the current environment. Preview URLs are available after the build completes.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 37 lines · 92 tokens per session scan A 6b052993eb96
catalyst-slate is a skill published in the GitHub repository catalystbyzoho/agent-skills (59 stars, last pushed 12d ago), licensed Apache-2.0. It adds 92 tokens to every session and 944 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-30.
Other skills, from other repositories
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
menu-transitions-rtl
Animate react-horizontal-scrolling-menu scrolling and build right-to-left menus: noPolyfill defaults to true since v8, so transitionDuration (default 500), a custom-easing-function transitionBehavior, and per-call ScrollOptions { duration, boundary } on scrollToItem/scrollNext/scrollPrev are silently ignored unless…