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/catalystbyzoho/claude-plugin/catalyst-authenticationnpx skills add catalystbyzoho/claude-plugin --skill catalyst-authenticationgit clone --depth 1 https://github.com/catalystbyzoho/claude-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/catalystbyzoho/claude-plugin/catalyst-authentication)<a href="https://agentmods.dev/skills/catalystbyzoho/claude-plugin/catalyst-authentication"><img src="https://agentmods.dev/badge/skills/catalystbyzoho/claude-plugin/catalyst-authentication.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.00113 | $0.00913 |
| Opus 5 | $0.00056 | $0.00456 |
| Sonnet 5 | $0.00023 | $0.00183 |
| Haiku 4.5 | $0.00011 | $0.00091 |
Grade A, and why
catalyst-authentication 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🚦 Local auth requires plain
catalyst serveAuth works locally only when the frontend is served through
catalyst serve; prefer plaincatalyst serveso Functions/AppSail run alongside Slate. NEVER use the native dev server (npm run dev,vite,next dev,ng serve, …) — it lacks the/__catalyst/sdk/init.jsendpoint, session cookie, ZAID, and managed-service proxy, so login/signup,getCurrentUser, andisUserAuthenticatedfail (401) though the page renders. If auth "doesn't work locally," check this first. See../catalyst-slate/.
How It Works
- Identify flow type — Hosted login (redirect to Catalyst login page), embedded login (custom UI), or backend
getCurrentUsercheck. - Load
references/auth-basics.md— for signup/login flows, ZAID gotcha, hosted vs embedded login, and common auth errors. - ZAID warning — ZAID differs between Development and Production. This is the #1 auth issue in production. Always verify the environment.
- Security Rules — If the query involves controlling who can invoke a function, route to
catalyst-functionsskill and its../catalyst-functions/references/functions-basics.mdSecurity Rules section. Security Rules has two parameters: (a)methods— which HTTP methods (GET/POST/PUT/DELETE/PATCH) are enabled for the function (removing a method blocks that verb entirely), and (b)authentication— a single binary flag (optional= public,required= authenticated users only) applied function-wide, not per-method. For role-based data access control, route to DataStore Scopes and Permissions (Console → Table → Scopes and Permissions). - OAuth / Connections — Load
references/connections.mdfor external API OAuth token management (Zoho or third-party).
Security Checklist
- Local auth requires
catalyst serve(never the native dev server) — see the 🚦 rule above. - ZAID is environment-specific. The Development ZAID is different from the Production ZAID. Social logins (Google, Facebook, LinkedIn, Microsoft) configured in Development MUST be reconfigured with the Production ZAID and production app domain before going live — using the wrong ZAID causes all social logins to silently fail in production.
- DataStore permissions are separate from function-level auth. Requiring authentication in Security Rules only controls who can call the function. App User table permissions (Console → Table → Scopes and Permissions) separately control which DataStore operations authenticated users can perform.
What ships with it
2 files 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.
- 4d ago First seen · 37 lines · 113 tokens per session scan A 9e10a8449e2d
catalyst-authentication is a skill published in the GitHub repository catalystbyzoho/claude-plugin (0 stars, last pushed 22d ago), licensed Apache-2.0. It adds 113 tokens to every session and 913 once invoked, about $0.0006 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
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…