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 commands/dashpay/platform/setupgit clone --depth 1 https://github.com/dashpay/platformWhat 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.00000 | $0.00520 |
| Opus 5 | $0.00000 | $0.00260 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
setup 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 yesterday.
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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
setup
The setup command initializes a new Dash node with the specified configuration preset.
Usage
dashmate setup [PRESET] [OPTIONS]
Arguments
| Argument | Description | Required | Default |
|---|---|---|---|
preset |
Node configuration preset (mainnet, testnet, local) |
No | Prompts if not provided |
Options
| Option | Description | Default |
|---|---|---|
-d, --debug-logs |
Enable debug logs | false |
--no-debug-logs |
Disable debug logs | |
-c, --node-count=<number> |
Number of nodes to setup (for local preset, minimum 3) |
|
-m, --miner-interval=<interval> |
Interval between blocks (for local preset) |
|
-v, --verbose |
Use verbose mode for output | false |
Description
The setup command configures a new Dash node with one of the following presets:
- mainnet: Run a node connected to the Dash main network
- testnet: Run a node connected to the Dash test network
- local: Run a full network environment on your machine for local development
If no preset is specified, the command will prompt you to select one.
For the local preset, you can specify how many nodes to create with the --node-count option. At least 3 nodes are required for proper operation.
The command prevents you from overwriting an existing configuration.
If a configuration for the specified preset already exists, the command will suggest using dashmate reset or dashmate group reset to start from scratch.
Examples
# Set up a mainnet node
dashmate setup mainnet
# Set up a testnet node with debug logs enabled
dashmate setup testnet --debug-logs
# Set up a local development environment with 3 nodes
dashmate setup local --node-count=3
# Set up a local environment with custom block mining interval
dashmate setup local --miner-interval=1m
Related Commands
- reset - Reset a node to its initial state
- config create - Create a new configuration
- group reset - Reset all nodes in a group
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.
- yesterday First seen · 63 lines · 0 tokens per session scan A 2d50b933b664
setup is a command published in the GitHub repository dashpay/platform (92 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 520 tokens. 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 commands, from other repositories
invariant
Generate Foundry invariant tests for property-based fuzzing. The high-value command for serious teams.
pre-deploy
Interactive pre-launch security checklist — walk the operational and code-safety gates and produce a final GO / NO-GO with each item PASS / FAIL / N-A.
audit-strict
Multi-pass consensus audit — runs the audit twice with different prompts, only reports consensus findings. Aggressively cuts false positives.
gas
Gas profile — find expensive operations and suggest optimizations with before/after numbers.
explain
Explain a finding in plain English, with examples. Optionally tailored to a beginner audience.
codespace-verify
Command "codespace-verify" from kota1026/quantum-shield, covering codespaces ui確認コマンド, 1. codespaces起動確認, サービス起動状態確認, postgresql, redis, rabbitmqが起動していない場合 and フロントエンド起動.