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-basicsnpx skills add catalystbyzoho/claude-plugin --skill catalyst-basicsgit 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-basics)<a href="https://agentmods.dev/skills/catalystbyzoho/claude-plugin/catalyst-basics"><img src="https://agentmods.dev/badge/skills/catalystbyzoho/claude-plugin/catalyst-basics.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.00081 | $0.01411 |
| Opus 5 | $0.00041 | $0.00705 |
| Sonnet 5 | $0.00016 | $0.00282 |
| Haiku 4.5 | $0.00008 | $0.00141 |
Grade A, and why
catalyst-basics 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚠️ PRE-FLIGHT CHECK: Before creating any project files, confirm that
.catalystrcandcatalyst.jsonexist in the project directory. If they don't:
- Use MCP (
CatalystbyZoho_List_All_Organizations→CatalystbyZoho_List_All_Projects) to list orgs/projects.- 🔒 Never assume the org/project. If there is no project initialized, or the project is ambiguous, STOP and ask the user which project (and org) to work in — a single project in the list is not permission to auto-select it; confirm first. Never infer the project from the directory name or a past session. (Full rule:
references/preflight.md→ Golden Rule.)- Only after the project is resolved and confirmed run:
catalyst init --org <orgId> -p <projectId> -ni- Never ask the user to run
catalyst initinteractively. Never create these files manually — they are CLI-generated and must come from the CLI.Always run the
catalystCLI in non-interactive mode. Every command takes a-ni/--non-interactiveflag (or setZCATALYST_NON_INTERACTIVE=1; requires CLI v1.27.0+) and accepts its inputs as flags, so the CLI never prompts. Interactive menus exist for humans only — agents must never rely on them. The one exception iscatalyst login, whose browser OAuth step needs the user. See the required flags per command inreferences/cli.md.
How It Works
- Pre-flight first — Establish and verify org/project context per the canonical sequence in
references/preflight.md(read.catalystrcfor org/project, confirm parity with MCP, or resolve via MCP if.catalystrcis absent). Use MCP for all other resource IDs instead of asking the user. - New to Catalyst? — If the user is setting up Catalyst for the first time or asking "how do I start", load
references/quick-start.mdfor the full walkthrough. - Console navigation — If the user asks how to find IDs, create tables, set permissions, or configure CORS in the console, load
references/console-ui-guide.md. - Project structure — Load
references/project-basics.mdfor directory layout,catalyst.json, IDs, and dev-to-prod checklist. - CLI questions — Load
references/cli.mdfor the exact command, flags, and safety rules. - Answer — Provide the specific ID path or CLI command needed. Never ask the user to manually look up IDs when MCP is connected.
What ships with it
10 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.
- references/architecture.md 5.9 KB
- references/cli.md 28 KB
- references/console-ui-guide.md 5.0 KB
- references/preflight.md 11 KB
- references/project-basics.md 18 KB
- references/quick-start.md 6.3 KB
- references/setup/claude-code.md 1.9 KB
- references/setup/cursor.md 1.5 KB
- references/setup/github-copilot.md 1.9 KB
- references/setup/setup-common.md 2.2 KB
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 · 57 lines · 81 tokens per session scan A 6958a69b419f
catalyst-basics is a skill published in the GitHub repository catalystbyzoho/claude-plugin (0 stars, last pushed 22d ago), licensed Apache-2.0. It adds 81 tokens to every session and 1,411 once invoked, about $0.0004 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…