Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/openclawby/tradingview-mcpnpx agentmods add skills/openclawby/tradingview-mcp/pine-developWrote 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/openclawby/tradingview-mcp/pine-develop)<a href="https://agentmods.dev/skills/openclawby/tradingview-mcp/pine-develop"><img src="https://agentmods.dev/badge/skills/openclawby/tradingview-mcp/pine-develop/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/openclawby/tradingview-mcp/pine-develop"><img src="https://agentmods.dev/badge/skills/openclawby/tradingview-mcp/pine-develop.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.00032 | $0.00583 |
| Opus 5.5 | $0.00013 | $0.00233 |
| Sonnet 5.5 | $0.00006 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
pine-develop 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 1mo 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
91% identical to pine-develop — 16 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pine Script Development Loop
You are developing a Pine Script indicator or strategy in TradingView. Follow this loop precisely.
Step 1: Understand the Goal
If not already clear, ask the user:
- What type? (indicator, strategy, library)
- What does it do? (entry/exit logic, overlay, oscillator, etc.)
- Overlay or separate pane?
- Any specific inputs or visual elements?
Step 2: Pull Current Source (if modifying)
If modifying an existing script:
node scripts/pine_pull.js
Then read scripts/current.pine to understand what's there.
If creating new: start from scratch.
Step 3: Write the Pine Script
Write the complete script to scripts/current.pine. Every script MUST include:
//@version=6header- Proper
indicator()orstrategy()declaration - All user inputs with
input.*()functions and groups - Clear comments for each logical section
For strategies, include:
strategy.entry()andstrategy.exit()calls- Position sizing via
strategy()declaration - Default commission and slippage settings
Step 4: Push and Compile
node scripts/pine_push.js
This injects the code into TradingView's Pine Editor, clicks compile, and reports any errors.
Step 5: Fix Errors
If errors are reported:
- Read the error messages (line number + description)
- Edit
scripts/current.pinelocally — fix the specific lines - Push again:
node scripts/pine_push.js - Repeat until 0 errors
Common Pine Script errors:
- "Mismatched input" — usually indentation (Pine uses 4-space indentation, not braces)
- "Could not find function or function reference" — typo in function name or wrong version
- "Undeclared identifier" — variable used before declaration
- "Cannot call X with argument type Y" — wrong parameter type
Step 6: Verify on Chart
After clean compilation:
capture_screenshot— take a screenshot to verify it looks rightdata_get_strategy_results— if it's a strategy, check performance- Show the user the results
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.
- 1mo ago First seen · 79 lines · 32 tokens per session scan A c46b887152aa
pine-develop is a skill published in the GitHub repository openclawby/tradingview-mcp (1 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 583 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to pine-develop, differing in 16 lines, and is treated as a copy.
Other skills, from other repositories
vnpy-export
Export a Vibe-Trading backtest strategy to a runnable vnpy CtaTemplate Python class — supports A-share equities, futures, and crypto via BarGenerator + ArrayManager.
yfinance
Skill "yfinance" from HKUDS/Vibe-Trading, covering yfinance, deep yahoo interfaces (references/), quick start, ticker format conversion and supported data types.
tqsdk-trading-and-data
Explain, implement, or debug TqSdk Python workflows for waitupdate or ischanging update loops, market data retrieval, historical download, account type selection, funds or positions or orders or trades, field meanings, order placement or cancellation, target-position tools, TqScenario margin trials, real-account…
miniqmt-to-bigqmt
A conversion guide for moving Python trading strategies from miniQMT, an external trading setup, into the Python environment built into bigQMT, a trading client. It covers code changes, compatibility checks, deployment, and live-trading verification.
alpaca-trade-api-sdk
Integrate and build on the @alpacahq/alpaca-trade-api TypeScript SDK for the Alpaca Trading and Market Data APIs (the unified Alpaca client, ergonomic order builders, normalized market-data shapes, pagination, typed errors, resilience, and real-time streaming). Use when writing or reviewing code that imports…
ai-code-assist
AI Code Assist enables traders to create custom strategies, indicators, and tools using natural language. No coding experience required. Based on TradingView's AI-assisted Pine Script development.