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/jamaljsr/polar/copilot-instructionsgit clone --depth 1 https://github.com/jamaljsr/polarWrote 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/jamaljsr/polar/copilot-instructions)<a href="https://agentmods.dev/instructions/jamaljsr/polar/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jamaljsr/polar/copilot-instructions.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.01129 | $0.01129 |
| Opus 5 | $0.00564 | $0.00564 |
| Sonnet 5 | $0.00226 | $0.00226 |
| Haiku 4.5 | $0.00113 | $0.00113 |
Grade A, and why
polar copilot-instructions.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 5d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Polar - AI Coding Assistant Instructions
Polar is a Bitcoin Lightning Network development tool that creates local regtest networks using Docker containers. This guide helps AI agents understand the architecture and contribute effectively.
Core Architecture
Network Orchestration via Docker Compose
- Networks are composed of Bitcoin nodes (bitcoind) and Lightning nodes (LND, Core Lightning, Eclair)
- Each network generates a
docker-compose.ymlfile with pre-configured containers - Node configurations are templated in
src/lib/docker/composeFile.tswith variable substitution - Lightning nodes auto-select compatible Bitcoin backends via
filterCompatibleBackends()
State Management (Easy-Peasy + Redux)
- Store Structure:
src/store/models/- modular stores for network, lightning, bitcoin, designer, mcp - Network Model: Manages network lifecycle, node creation, Docker orchestration
- Designer Model: Handles visual chart state, drag-drop interactions, node positioning
- Key Pattern: Actions update state → triggers React re-renders → auto-saves via debounced effects
Visual Designer (React Flow Chart)
- Network topology represented as interactive graph in
src/components/designer/NetworkDesigner.tsx - Drag-drop from sidebar adds nodes via
onCanvasDrop→ creates loading node → async node creation → replaces with real node - Chart state syncs with network model; positions persisted to disk
- Custom components:
NodeInner,Link,Portfor Bitcoin/Lightning-specific rendering
Development Patterns
Node Creation Workflow
- User drags node type from sidebar →
onCanvasDroptriggered - Temporary loading node added to chart
network.addNode()creates node in network model- Docker compose file regenerated via
dockerService.saveComposeFile() - If network running, node auto-starts via
toggleNode() - Loading node replaced with actual node in chart
Testing Strategy
- Unit Tests: Jest with React Testing Library, emphasis on Redux action/state testing
- Mocks: Extensive Docker service mocking in
src/__mocks__/ - Test Utilities:
src/utils/tests/provides network factories, state builders, async helpers
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.
- 5d ago First seen · 100 lines · 1,129 tokens per session scan A b48ea1acd335
polar copilot-instructions.md is an instructions file published in the GitHub repository jamaljsr/polar (858 stars, last pushed yesterday), licensed MIT. It adds 1,129 tokens to every session, about $0.0056 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
rakazo AGENTS.md
AGENTS.md instructions for elie222/rakazo, a project described as: Open-source Grok Bot alternative. Choose your own model and sandbox.
vellium AGENTS.md
AGENTS.md instructions for tg-prplx/vellium, covering agents.md — vellium contributor and coding-agent guide, 1. product and runtime model, 2. start every task safely, 3. repository map and renderer: src/.
Netcatty AGENTS.md
AGENTS.md instructions for binaricat/Netcatty, covering agents overview, current agents (roles), how things talk, ai agent harness (infrastructure/ai/harness/) and codex app server (experimental).
Netcatty CLAUDE.md
Claude Code instructions for binaricat/Netcatty, covering claude.md, commands, install dependencies, lint and run all tests.
cc-mascot CLAUDE.md
Claude Code instructions for kazakago/cc-mascot, covering cc mascot - 技術ドキュメント, プロジェクト概要, コンセプト, 技術スタック and アーキテクチャ概要.
SaturnZap copilot-instructions.md
Instructions for lqwdtech/SaturnZap, covering saturnzap — copilot instructions, build & test, architecture, conventions and test patterns.