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-signalsnpx skills add catalystbyzoho/claude-plugin --skill catalyst-signalsgit 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-signals)<a href="https://agentmods.dev/skills/catalystbyzoho/claude-plugin/catalyst-signals"><img src="https://agentmods.dev/badge/skills/catalystbyzoho/claude-plugin/catalyst-signals.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.1 | $0.00107 | $0.00877 |
| Opus 5 | $0.00053 | $0.00439 |
| Sonnet 5 | $0.00021 | $0.00175 |
| Haiku 4.5 | $0.00011 | $0.00088 |
Grade A, and why
catalyst-signals 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 6d 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.
This is a copy
94% identical to catalyst-signals — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prerequisites
Before using Signals, activate it once per project in the console:
Console → your project → Signals (left sidebar) → click "Start Exploring"
Skipping this step prevents access to Publishers, Webhooks, Rules, and Logs. This is a one-time activation per project.
How It Works
-
Console-Only Service — HARD STOP if user expects SDK/API. Catalyst Signals is configured entirely through the Catalyst Console — there is NO SDK, REST API, or programmatic interface for creating publishers, rules, or webhooks. All setup is done via the console UI.
- Publishers, events, webhooks, and rules are created in Console → Signals
- Functions and Circuits are created separately in Console → Serverless, then selected as targets in Signals rules
- The only code-level interaction is receiving events in target functions/circuits
-
Understand the flow — Publisher → Event → Rule (with filters/transforms) → Target (Webhook/Function/Circuit)
-
Load
references/signals-basics.md— for publishers (Zoho/Catalyst/Custom), events, rules, targets, dispatch policies, event statuses, and deployment gotchas -
Key concepts:
- Publishers emit events when actions occur (3 types: Zoho, Catalyst CloudScale, Custom)
- Events are JSON payloads with auto-generated schemas (max 100KB for Zoho, 64KB for Custom)
- Rules connect publishers to targets with optional filters and payload transformations
- Targets receive events via Webhooks, Functions, or Circuits
- Dispatch Policy controls event delivery: Instant (deliver immediately) or Batch (aggregate events — by count, size, interval, or schedule)
-
Deployment warning — Rules are locked in production (enable/disable only). All rule changes must be made in Development and deployed. Max 25 publishers per deployment.
Security Checklist
- Custom publisher REST API rate limit: 500 requests per minute. Exceeding this locks the API URL for 60 seconds.
- Environment-specific REST API URLs: Custom event REST API URLs differ between Development and Production — update URLs when deploying.
- Function/Circuit targets inherit their own permissions: If a function is the target, it runs with whatever scope it was configured with (user or admin). Signals does not override function-level permissions.
- Event payload size limits: Zoho publishers max 100KB per event (5MB for multi-event batch). Custom publishers max 64KB per event (256KB for up to 25 events).
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.
- 6d ago First seen · 52 lines · 107 tokens per session scan A 4bffa525ffc2
catalyst-signals is a skill published in the GitHub repository catalystbyzoho/claude-plugin (1 stars, last pushed 25d ago), licensed Apache-2.0. It adds 107 tokens to every session and 877 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to catalyst-signals, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
omni-mcp
Connect to the OmniRoute MCP server (110 tools, 3 transports: SSE/stdio/HTTP). Covers routing, cache, compression, memory, skills, providers, and audit tools across 33 permission scopes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.