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 instructions/trugurpala/pinescriptv6/gemini-mdgit clone --depth 1 https://github.com/trugurpala/pinescriptv6Wrote 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/instructions/trugurpala/pinescriptv6/gemini-md)<a href="https://agentmods.dev/instructions/trugurpala/pinescriptv6/gemini-md"><img src="https://agentmods.dev/badge/instructions/trugurpala/pinescriptv6/gemini-md.svg" alt="Measured on agentmods" 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 | $0.03273 | $0.03273 |
| Opus 5 | $0.01636 | $0.01636 |
| Sonnet 5 | $0.00655 | $0.00655 |
| Haiku 4.5 | $0.00327 | $0.00327 |
Grade A, and why
pinescriptv6 GEMINI.md 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 4d 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
92% identical to pinescriptv6 copilot-instructions.md — 6 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pine Script Agent Kit context for Gemini CLI
This file is repository context. Prefer the canonical catalogs when another instruction surface differs.
Evidence-first operating protocol
You are working with Pine Script v6. Treat knowledge/catalog.json as the
canonical rule index and knowledge/sources.json as the canonical source index.
- Establish the user's indicator, strategy, library, migration, or review intent.
- Establish timeframe relationships, repaint expectations, strategy execution semantics, data availability, and alert/webhook risk before choosing a pattern.
- Apply only rules whose scope matches. Preserve each rule's exceptions.
- Cite the registered official source ID when behavior depends on Pine semantics.
- Label local static results
structural-only. Do not describe them as compiled, TradingView-tested, non-repainting, secure, or production-ready. - Treat a hash-matching record in
verification/tradingview.jsonas manual evidence only for the recorded file and environment. - If sources conflict, a source is unavailable, or intent is ambiguous, narrow the claim and state what remains unverified.
- Never expose credentials or place real webhook secrets in code or output.
- Prefer a minimal change, include a validation path, and separate code-ready, tested, published, and live states.
The project is independent and is not affiliated with or endorsed by TradingView.
Active sourced rules
PSAK-ALERT-001 — Selectable alertcondition events
alertcondition() calls create separately selectable conditions in indicators; calls in a strategy do not create selectable alertcondition alerts.
Scope: Pine v6 indicator and strategy alert API selection.
Why: The alert creation UI exposes indicator alertcondition() events separately, while strategy alert choices use other event mechanisms.
Exceptions:
- A strategy can still compile with alertcondition(); strategies can expose alert() calls and broker-emulator order-fill events.
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.
- 4d ago First seen · 317 lines · 3,273 tokens per session scan A 5e9a3d2d2325
pinescriptv6 GEMINI.md is an instructions file published in the GitHub repository trugurpala/pinescriptv6 (2 stars, last pushed 1mo ago), licensed MIT. It adds 3,273 tokens to every session, about $0.0164 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to pinescriptv6 copilot-instructions.md, differing in 6 lines, and is treated as a copy.
Other instructions, from other repositories
apm python.instructions.md
Python development guidelines.
apex-accelerator vendor-prompting.instructions.md
Vendor prompting best-practice rules for Anthropic Claude and OpenAI GPT-5.6-Terra agents and prompts. Each rule cites a rule ID in the vendor-prompting skill rules.json registry. Validator: npm run lint:vendor-prompting.
matt-skills-with-to-goal CLAUDE.md
Instructions for tt-a1i/matt-skills-with-to-goal: Skills are organized into bucket folders under skills/.
ephemeral-sandbox CLAUDE.md
Instructions for Ephemeral-AI-Lab/ephemeral-sandbox, covering claude.md, project, engineering practice (required), build & test and sandbox tools.
martex-quant CLAUDE.md
Instructions for martex-dev/martex-quant, covering session start — read these first, project instructions, ai trading bot project - master instructions, role and project objective.
pixir CLAUDE.md
Instructions for Ranvier-Technologies/pixir, covering pixir harness - legacy agent guide, current map and commands.