Updated Jul 15, 2026

Utilities

Compare this run to a Trickest storage baseline

Diff this run against a Trickest storage baseline.

Agent

overview

What diff-trickest-files does

diff-trickest-files is the managed Utilities node that compares this run's new-file to a named old-file in Trickest storage and writes only the lines that differ.

A scheduled recon or inventory job that should probe, screenshot, or alert on deltas, not the full historical set every cycle.

Authenticate with token or token-file. Refresh the baseline with put-trickest-files after each run. For a pull without comparison, use get-trickest-files.

use cases

Where diff-trickest-files fits

Surface only newly discovered assets

Diff this run's subdomain list against the version stored last run so probing and alerting fire on new hosts, not the full set every time.

Build continuous attack-surface monitoring

Schedule a recon workflow and diff each output against its stored baseline to catch changes as they appear across the estate.

Cut downstream cost on large datasets

Feed only the changed lines to expensive nodes like screenshotting or scanning instead of rerunning them over unchanged data.

Keep a durable baseline across runs

Store the latest list with put-trickest-files after the diff so the next scheduled run has a current old-file to compare against.

reference

diff-trickest-files inputs and flags

4 inputs
NameTypeFlagDescription
new-fileFILE·The new file produced by the current run.
old-fileSTRING·Name of the baseline file as saved in Trickest file storage.
tokenSTRING·Trickest authentication token.
token-fileFILE·Trickest authentication token supplied as a file.

Showing key inputs. diff-trickest-files exposes 4 inputs in total.

example

Run diff-trickest-files

diff-trickest-files · command
# compare this run's subdomain list to the stored baseline named subdomains.txtdiff-trickest-files new-subs.txt subdomains.txt
sample output
api.example.comstaging.example.comcdn.example.com198.51.100.42vpn.example.comdev.example.com203.0.113.17

guidance

Choosing diff-trickest-files

Use diff-trickest-files when a scheduled workflow should act only on what changed since the last run. Store a baseline with put-trickest-files, diff the next run against it, then refresh the baseline. To pull a stored file without comparing, use get-trickest-files.

get-trickest-files

Pulls a stored file into the workflow. Use when you need the baseline itself, not a delta.

put-trickest-files

Saves a file to storage. Run after the diff to keep the baseline current.

anew

Appends only new lines to a local file. Prefer anew for in-run merges; prefer this node for a persisted storage baseline.

faq

diff-trickest-files questions

new-file is this run's output. old-file is the exact name of a baseline already saved in Trickest storage. The node returns the lines that differ.

Run diff-trickest-files yourself

A fresh subdomain list feeds diff-trickest-files, which compares it to the stored baseline and writes only the changed lines as output.

Facts on this page come from the live Trickest tool library.