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/openclawby/tradingview-mcp/pine-developnpx skills add openclawby/tradingview-mcp --skill pine-developgit clone --depth 1 https://github.com/openclawby/tradingview-mcpWhat 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 | $0.00032 | $0.00583 |
| Opus 5 | $0.00016 | $0.00292 |
| Sonnet 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 2d 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.
- 2d 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 (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 583 once invoked, about $0.0002 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.