SaturnZap tests.instructions.md

A set of instructions for writing and debugging SaturnZap tests. SaturnZap is a Python application for using the Lightning Network, a payment network built on Bitcoin.

In plain words
What is it for?
Use it when adding or fixing SaturnZap tests, testing its command-line interface, resetting test state, or simulating wallet and Lightning-node responses.
Why use it?
It keeps tests consistent by documenting the project's fixtures, command-line testing approach, and ways to replace the Lightning node with a mock.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/lqwdtech/saturnzap/tests
Clone the repo
git clone --depth 1 https://github.com/lqwdtech/SaturnZap

Made for: GitHub Copilot.

Per session 606 This file is loaded in full into every session.
When invoked 606 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00606 $0.00606
Opus 5 $0.00303 $0.00303
Sonnet 5 $0.00121 $0.00121
Haiku 4.5 $0.00061 $0.00061

Measured 3d ago against content hash 0daf2da4943c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

SaturnZap tests.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 3d 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.

.github/instructions/tests.instructions.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Test Conventions

Fixtures (autouse)

conftest.py provides three autouse fixtures that reset state between tests:

  • _reset_active_network (conftest.py) — resets config._active_network to None
  • _clean_data_dir (per-file) — redirects XDG_DATA_HOME to tmp_path (no real seed touched)
  • _reset_pretty (per-file) — resets output._pretty to False
  • _reset_node (per-file) — resets node._node and node._ipc_mode singletons

New test files automatically pick these up. If a test needs the real data dir, override _clean_data_dir locally.

CLI Testing

from typer.testing import CliRunner
from saturnzap.cli import app

runner = CliRunner()
result = runner.invoke(app, ["balance"])
data = json.loads(result.output)
assert data["status"] == "ok"

Mocking LDK Node

Use unittest.mock.MagicMock with types.SimpleNamespace for nested return values:

n = MagicMock()
n.node_id.return_value = "02abc"
n.list_balances.return_value = SimpleNamespace(
    total_onchain_balance_sats=100_000,
    spendable_onchain_balance_sats=90_000,
    total_lightning_balance_sats=50_000,
    total_anchor_channels_reserve_sats=0,
)

Patch at the consumer: @patch("saturnzap.node.Builder"), not the ldk_node import.

ANSI Stripping

NO_COLOR=1 is set in conftest. For extra safety, use strip_ansi():

from tests.conftest import strip_ansi
assert "init" in strip_ansi(result.output)

Markers

  • @pytest.mark.live — requires running droplet nodes. Deselected in CI with -m "not live".
  • No marker needed for unit tests (default).

Assertions

  • Parse JSON output: json.loads(result.output) or json.loads(capsys.readouterr().out)
  • Check error output on stderr: json.loads(capsys.readouterr().err)
  • File permissions: assert (path.stat().st_mode & 0o777) == 0o600

Don'ts

  • Don't create a new conftest.py — extend the root one
  • Don't mock at the ldk_node package level — mock at saturnzap.node or saturnzap.cli
  • Don't skip the _clean_data_dir fixture unless testing real filesystem behavior

Read the full file on GitHub · 73 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. 3d ago First seen · 73 lines · 606 tokens per session scan A 0daf2da4943c

Subscribe to this mod's changes

SaturnZap tests.instructions.md is an instructions file published in the GitHub repository lqwdtech/SaturnZap (7 stars, last pushed 17d ago), licensed MIT. It adds 606 tokens to every session, about $0.0030 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.