pine-develop

pine-develop is a skill for Claude Code, Codex from openclawby/tradingview-mcp. It costs 32 tokens per session (583 once invoked), scanned A, a copy of pine-develop, Apache-2.0.

A step-by-step workflow for building Pine Script indicators and strategies in TradingView. Pine Script is TradingView’s language for creating custom chart studies and trading systems.

In plain words
What is it for?
Use it to create or modify indicators, strategies, or libraries; pull existing code; add inputs and trading rules; push code to TradingView; and verify compilation.
Why use it?
It provides a repeatable loop for defining the goal, writing the script, compiling it, and fixing errors until it works.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node scripts/pine_pull.js.

Good fit Use it to create or modify indicators, strategies, or libraries; pull existing code; add inputs and trading rules; push code to TradingView; and verify compilation.

Compare 6 skills from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/openclawby/tradingview-mcp
agentmods
npx agentmods add skills/openclawby/tradingview-mcp/pine-develop

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for pine-develop

README.md
[![agentmods](https://agentmods.dev/badge/skills/openclawby/tradingview-mcp/pine-develop/github.svg)](https://agentmods.dev/skills/openclawby/tradingview-mcp/pine-develop)
Your own site
<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.

agentmods 80×15 button for pine-develop

Your own site · 80×15
<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>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 583 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 1mo ago against content hash c46b887152aa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

Origin

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.

skills/pine-develop/SKILL.md · 79 lines

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=6 header
  • Proper indicator() or strategy() declaration
  • All user inputs with input.*() functions and groups
  • Clear comments for each logical section

For strategies, include:

  • strategy.entry() and strategy.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:

  1. Read the error messages (line number + description)
  2. Edit scripts/current.pine locally — fix the specific lines
  3. Push again: node scripts/pine_push.js
  4. 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:

  1. capture_screenshot — take a screenshot to verify it looks right
  2. data_get_strategy_results — if it's a strategy, check performance
  3. Show the user the results

Read the full file on GitHub · 79 lines

Changes

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.

  1. 1mo ago First seen · 79 lines · 32 tokens per session scan A c46b887152aa

Subscribe to this mod's changes

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.

Related

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.

HKUDS/Vibe-Trading · 40 tokens

yfinance

Skill "yfinance" from HKUDS/Vibe-Trading, covering yfinance, deep yahoo interfaces (references/), quick start, ticker format conversion and supported data types.

HKUDS/Vibe-Trading · 41 tokens

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…

shinnytech/tqsdk-python · 286 tokens

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.

litaolemo/xtquant_big_convert · 144 tokens

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…

alpacahq/alpaca-trade-api-js · 123 tokens

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.

Signal-Execution-Labs/forex-trading-ai-agent · 0 tokens