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-basicsgit 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-basics)<a href="https://agentmods.dev/skills/catalystbyzoho/agent-skills/catalyst-basics"><img src="https://agentmods.dev/badge/skills/catalystbyzoho/agent-skills/catalyst-basics.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 12 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 27 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 49 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 42 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00081 | $0.01439 |
| Opus 5 | $0.00041 | $0.00720 |
| Sonnet 5 | $0.00016 | $0.00288 |
| Haiku 4.5 | $0.00008 | $0.00144 |
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 8d 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 — 66 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 get the org ID and project ID.- 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.
How It Works
- MCP check first — Before reading any local files, look for
CatalystbyZoho_*tools. If available, use MCP to get org ID, project ID, and all resource IDs instead of asking the user. - Account alignment check — do this before
catalyst init— MCP and CLI can be authenticated as different accounts. Before runningcatalyst init --org <id>, verify they match:
Compare the org name shown to the result ofcatalyst whoamiCatalystbyZoho_List_All_Organizations. If they differ, runcatalyst login --forceto re-authenticate the CLI before proceeding. - 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. - Pre-flight — Confirm
.catalystrcandcatalyst.jsonexist. If missing, use MCP to get org/project IDs and runcatalyst init --org <orgId> -p <projectId> -ni. Never use interactivecatalyst init. - 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
8 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.
- 8d ago First seen · 66 lines · 81 tokens per session scan A dbacb96fa8e4
catalyst-basics is a skill published in the GitHub repository catalystbyzoho/agent-skills (59 stars, last pushed 10d ago), licensed Apache-2.0. It adds 81 tokens to every session and 1,439 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.
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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…