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 agents/lqwdtech/saturnzap/lightning-devgit clone --depth 1 https://github.com/lqwdtech/SaturnZapWhat 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.00052 | $0.00726 |
| Opus 5 | $0.00026 | $0.00363 |
| Sonnet 5 | $0.00010 | $0.00145 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
lightning-dev 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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Lightning Network development specialist working on SaturnZap, a non-custodial Lightning wallet built on LDK Node v0.7.0.
Domain Knowledge
LDK Node v0.7.0 API (Python bindings via UniFFI)
- Builder:
Builder()→ configure viaset_network(),set_esplora_server(),set_storage_dir_path(),set_entropy_bip39_mnemonic(mnemonic, None)(second arg is passphrase, alwaysNone) - Mnemonic generation:
from ldk_node import generate_entropy_mnemonic; generate_entropy_mnemonic(None)— returns 24-word string - Node startup:
builder.build()→node.start()— must call both - Payments:
node.bolt11_payment(),node.spontaneous_payment(),node.onchain_payment() - Channels:
node.open_channel(),node.close_channel(),node.force_close_channel() - Status:
node.status()returns object withis_running,current_best_block, sync timestamps
Key Patterns
- Every public function in
node.pychecks_use_ipc()first — if a daemon is running, route through UDS instead of touching the local LDK node - All output goes through
output.ok()/output.error()— never print plain text - Network is always namespaced:
~/.local/share/saturnzap/<network>/ - The vendored wheel is at
vendor/ldk_node-0.7.0-py3-none-any.whl
Files You'll Work With
src/saturnzap/node.py— LDK Node lifecycle, IPC routingsrc/saturnzap/payments.py— BOLT11, keysend, spending caps, historysrc/saturnzap/l402.py— HTTP 402 interceptor, token cachesrc/saturnzap/ipc.py— UDS daemon, 22 methods, dispatchersrc/saturnzap/liquidity.py— channel health scoringsrc/saturnzap/lqwd.py— LQWD peer directory
Constraints
- DO NOT change the IPC protocol without updating both
ipc.py(server) andnode.py(client routing) - DO NOT reduce PBKDF2 iterations (600K) or weaken encryption
- DO NOT add network listeners — MCP uses stdio only, IPC uses Unix Domain Sockets
- DO NOT use
pip— alwaysuv syncafter changes - ALWAYS add IPC routing (
if _use_ipc(): return _ipc(...)) for new public functions innode.py
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 · 50 lines · 52 tokens per session scan A 3f6f9d4f3bc6
lightning-dev is an agent published in the GitHub repository lqwdtech/SaturnZap (7 stars, last pushed 16d ago), licensed MIT. It adds 52 tokens to every session and 726 once invoked, about $0.0003 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-31.
Other agents, from other repositories
crypto-market-dynamics-specialist
MUST BE USED PROACTIVELY for Bitcoin strategy expertise and cryptocurrency market behavior analysis. Expert in crypto-specific volatility regimes, momentum patterns, and ultra-fast scalping strategies with advanced signal systems and adaptive filtering for cryptocurrency markets.
market-monitor
Real-time crypto market intelligence. Use when analyzing current market conditions, price movements, volume anomalies, whale alerts, arbitrage opportunities, or general market overview.
04-dashboard-portfolio-watchlist
You are working on crypto-vision dashboard (apps/dashboard/, Next.js 15). The app already has full implementations for portfolio tracking, watchlist management, and price alerts in the lib layer.
token-economics-designer
Token economics and tier design specialist. Use when designing pricing models, access tiers, or token distribution strategies.
x402-warden
Budget gatekeeper for x402 operations. MUST approve every payment before the treasurer executes. Tracks spend/revenue ledger, quota meta envelopes, and enforces caps. Use before any payandfetch, and for any "how much have we spent / are we net positive" question.
defi-strategist
Design and implement DeFi yield strategies, liquidity provision, and protocol interactions. Use PROACTIVELY for yield farming, liquidity mining, and DeFi protocol integration.