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 Sundeepg98/kite-mcp-server --skill alert-playbookgit clone --depth 1 https://github.com/Sundeepg98/kite-mcp-serverWrote 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/sundeepg98/kite-mcp-server/alert-playbook)<a href="https://agentmods.dev/skills/sundeepg98/kite-mcp-server/alert-playbook"><img src="https://agentmods.dev/badge/skills/sundeepg98/kite-mcp-server/alert-playbook/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/sundeepg98/kite-mcp-server/alert-playbook"><img src="https://agentmods.dev/badge/skills/sundeepg98/kite-mcp-server/alert-playbook.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.00103 | $0.01301 |
| Opus 5 | $0.00051 | $0.00651 |
| Sonnet 5 | $0.00021 | $0.00260 |
| Haiku 4.5 | $0.00010 | $0.00130 |
Grade A, and why
alert-playbook 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 11d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Alert Playbook
Three alert systems coexist in this MCP server. Pick the right one for the job.
1. Decide which alert type
| System | Trigger | Notification | Survives Kite token expiry? | Best for |
|---|---|---|---|---|
Server-managed alert (set_alert) |
Price above/below, % drop/rise with ref price | Telegram (if setup_telegram done), server log |
Yes — server polls Kite; on token expiry it stops and notifies | Casual price watching, percentage-change triggers, portfolio-wide monitoring |
Kite native alert (place_native_alert) |
Price above/below, % change, LTP cross | Native Kite push/email (ATO) | Yes — lives inside Zerodha, independent of our server | Long-running alerts you want regardless of our server uptime |
GTT (place_gtt_order) |
Price trigger → order placed | Order placement (SMS/email from Kite) | Yes — Kite manages it | Stop-losses, target exits, buy-on-dip setups with a pre-decided action |
Rule of thumb: if the alert should trigger an order, use GTT. If it just needs to ping you, use a server-managed or native alert.
2. Setting a server-managed alert
- If Telegram isn't wired yet, walk the user through
setup_telegramfirst (they need to DM the bot to get a chat_id). - Call
set_alertwith:instrument— e.g.,NSE:RELIANCEcondition—above,below,drop_pct,rise_pctvalue— price for above/below, percent for drop/risereference_price— required for drop_pct / rise_pct (anchors the % change)
- Confirm with
list_alerts.
Example: "Alert me when RELIANCE drops 3% from 1400"
→ condition: drop_pct, value: 3, reference_price: 1400
3. Setting a Kite native alert
Use when the user wants Zerodha to own the alert (survives our server restarts, hosted outside our infra):
- Call
place_native_alertwith the instrument, trigger type, and trigger value. - Notifications go via Kite's own push/email channels — not Telegram.
- Manage via
list_native_alerts/modify_native_alert/delete_native_alert.
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.
- 11d ago First seen · 102 lines · 103 tokens per session scan A b40de9972bd8
alert-playbook is a skill published in the GitHub repository Sundeepg98/kite-mcp-server (0 stars, last pushed 2mo ago), licensed MIT. It adds 103 tokens to every session and 1,301 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other skills, from other repositories
quant-mathematician
You are a world-class applied mathematician, statistical researcher, and quantitative strategy architect.
position-optimizer
You are a top 0.1% quantitative position-sizing and risk-optimization agent.
ai-trading-agent
You are an AI trading research assistant connected to Trader Dev MCP.
strategy-optimizer
You are a top 0.1% quantitative strategy optimization agent.
mean-reversion-engineer
You are a top 0.1% quantitative trading engineer and Pine Script developer.
ai-hedge-fund
You are the manager of an AI-powered hedge fund research desk.