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 Growth-Circle/cadis --skill cadis-protocolgit clone --depth 1 https://github.com/Growth-Circle/cadisWrote 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/growth-circle/cadis/cadis-protocol)<a href="https://agentmods.dev/skills/growth-circle/cadis/cadis-protocol"><img src="https://agentmods.dev/badge/skills/growth-circle/cadis/cadis-protocol/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/growth-circle/cadis/cadis-protocol"><img src="https://agentmods.dev/badge/skills/growth-circle/cadis/cadis-protocol.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.00265 |
| Opus 5 | $0.00017 | $0.00133 |
| Sonnet 5 | $0.00007 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
cadis-protocol 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 9d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 9d ago First seen · 52 lines · 34 tokens per session scan A 29f9bec4db92
cadis-protocol is a skill published in the GitHub repository Growth-Circle/cadis (57 stars, last pushed 20d ago), with no licence file. It adds 34 tokens to every session and 265 once invoked, about $0.0002 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
contract-test-engineer
Use when the user asks to verify compatibility between an API provider and consumer, SDK and service, event producer and consumer, schema versions, or serialized data. Define and test the shared contract, including failures and compatibility rules, before changing either side.
api-designer
An API contract design guide for planning how software interfaces work before implementation. An API is an agreed way for programs or clients to exchange requests and responses.
api-reviewer
Use when the user asks to review or change an HTTP, RPC, event, CLI, or SDK API contract. Inspect routes, schemas, authorization, errors, compatibility, and consumers before editing, then verify request and response behavior with focused tests.
architecture-designer
Use when the user asks to design, compare, or revise a system architecture, component boundary, data flow, integration, or technical decision. Inspect the current topology and constraints first, make tradeoffs explicit, and define verification and migration paths before implementation.
fullstack-dev
Implement features that span backend and frontend together — API endpoints with their UI, auth flows, CRUD modules, validation. Use when the subtask requires both sides of the system to ship a working feature.
python-sdk
Implement or modify Python SDK behavior under python/composio, including tools, toolkits, sessions, auth configs, connected accounts, client integration, and shared Python models. Use for Python core runtime/API work; pair with python-testing and cross-sdk-parity when TypeScript must match.