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-datastoregit 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-datastore)<a href="https://agentmods.dev/skills/catalystbyzoho/agent-skills/catalyst-datastore"><img src="https://agentmods.dev/badge/skills/catalystbyzoho/agent-skills/catalyst-datastore.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 28 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.00145 | $0.01100 |
| Opus 5 | $0.00072 | $0.00550 |
| Sonnet 5 | $0.00029 | $0.00220 |
| Haiku 4.5 | $0.00015 | $0.00110 |
Grade A, and why
catalyst-datastore 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚠️ PREREQUISITES — READ THIS FIRST
Before ANY Data Store operation, you MUST verify MCP connectivity.
- Search for
CatalystbyZoho_*tools in your available tool list. - If NOT found: STOP. Do NOT write any code, scaffold files, or instruct Console steps. Load
catalyst-zoho-mcpskill and guide the user through MCP setup. Do NOT proceed until the user confirmsCatalystbyZoho_*tools are visible. - If found: Run
CatalystbyZoho_List_All_Organizations→CatalystbyZoho_List_All_Projectsto set project context, then continue to "How It Works".
Execution Checklist (MUST follow in order)
- Step 0: Confirm
CatalystbyZoho_*tools visible → if none found → STOP, set up MCP first - Step 1: Run
CatalystbyZoho_List_All_Organizations - Step 2: Run
CatalystbyZoho_List_All_Projects - Step 3: For table creation →
CatalystbyZoho_Create_Table| For existing tables →CatalystbyZoho_List_All_Tables - Step 4: Proceed with the operation
How It Works
- Create or locate the table via MCP — Creating a table? Use
CatalystbyZoho_Create_Tabledirectly. Do NOT instruct the user to open the Catalyst Console or create the table manually. Reading/writing data? UseCatalystbyZoho_List_All_Tablesto get table IDs. Never ask the user to copy table IDs. - Load
references/datastore-basics.md— for CRUD operations, ZCQL syntax, result unwrapping, and permissions setup. - Unwrap ZCQL results — Always remind:
rows.map(r => r.TableName). Raw ZCQL results are wrapped; accessing without unwrapping is the #1 Data Store bug. - Permissions — App User permissions are OFF by default. If the query involves a logged-in user reading data, check Console → Table → Scopes & Permissions.
- Pagination — ZCQL max 300 rows per query. Use
LIMIT offset, countfor larger datasets.
Hallucination Guards
Never assert project-specific values from an empty or unread directory. If the working directory has no project files, do not invent or assume timezone, table names, project ID, environment names, or any other project-specific detail. Ask the developer to supply them.
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.
- 8d ago First seen · 57 lines · 145 tokens per session scan A 12688f9af7a5
catalyst-datastore is a skill published in the GitHub repository catalystbyzoho/agent-skills (59 stars, last pushed 10d ago), licensed Apache-2.0. It adds 145 tokens to every session and 1,100 once invoked, about $0.0007 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
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
convex-explain-app
Explain an existing Convex app — data model + relationships, public vs internal functions, auth/ownership model, components, a request→data flow — read from the schema and function surface. Read-only.
platform-custom-field-generate
Use this skill when users need to create, generate, or validate Salesforce Custom Field metadata. Trigger when users mention custom fields, field types, Roll-up Summary fields, Master-Detail relationships, Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from…
openloomi-api
OpenLoomi ships a local-first HTTP API served from the desktop app (port 3414, fallback 3515). All auth, Memory, AI, RAG, Loop, and Audit data live in a local SQLite database — your data stays on your machine and the OpenLoomi app is the source of truth. The only externally-routed auth path is the Composio OAuth…
nornicdb-grpc
Drive NornicDB over gRPC — the Qdrant-compatible surface (Collections, Points, Snapshots) plus the additive NornicSearch service. Use when ingesting via Qdrant SDKs, migrating from Qdrant, or running hybrid text+vector search from a non-Bolt client. Covers connection, RPC catalog, collection→database mapping…
field-service-sobject-create-configure
Headless 360 REST API deployment step for creating sObject records. Handles describe-based field discovery, required-field derivation, entity-relationship ordering, and composite graph transactions. Use this skill when a designer skill (or a user directly) needs to create sObject records after design confirmation…