Modular CLI workflow orchestration

Reckoning Orchestrator for offensive operations, reconnaissance, and monitoring

Reckoning helps you build repeatable workflows around command-line tools. It was designed with Red Team, penetration testing, and threat intelligence in mind—while staying general enough for any operation that benefits from structured, shareable execution.

Get started See capabilities Execution modes

At a glance

Workflow-first UI

Create ordered tool chains and follow progress per execution.

String substitution

Pass inputs and outputs between tools using {0}, {1}, {2}…

Recurring and scheduled runs

Run once, run continuously every N minutes, or run N times with intervals.

Designed to reduce friction in repeatable operations—without forcing you into a single tooling ecosystem.

Core features

Tool registry

Define tools by name, path, arguments, and update commands. Reckoning executes them consistently and captures results per step.

Store repeatable arguments
Update tooling via configured commands
Keep operations reproducible

Wordlists and variables

Map friendly names to paths (or values) and reference them in commands through simple substitution.

Short aliases for large paths
Use the same mechanism for API keys/tokens
Reduce manual typing and mistakes

Workflows

Compose a sequence of tools, choose their order, and run the workflow with a single execution.

Visual organization (including colors)
Execution history
Operational consistency across runs

Reckoning is an orchestrator. It does not replace tooling choices; it standardizes how you chain and execute them.

Workflow execution modes

Run once

The default behavior: execute the workflow a single time and store the full run history.

Recurring

Run continuously every N minutes. Useful for monitoring, recurring recon, and scheduled collection.

Run N times

Execute a fixed number of runs with N-minute sleeps between each run.

Substitution model

Reckoning uses a simple substitution model so that tools can consume each other’s outputs without custom glue code:

# {0} is the initial input (for example, a domain).
# {1}, {2}, ... are outputs from earlier tools in the workflow.

subfinder -d {0} -silent
httpx -l {1} -silent
nuclei -l {2} -severity medium,high,critical -jsonl
            

Wordlist aliases (and even API keys) can be referenced as {name}, resolving to the configured path/value.

Install and run

1) Clone

git clone https://github.com/rf-peixoto/reckoning

2) Install

./install.sh

3) Start

./start.sh

Open your browser at http://localhost:5000 after starting the service.

Security and responsible use

Reckoning is intended for legitimate security work: authorized offensive testing, reconnaissance, monitoring, and threat intelligence. Treat workflows as executable operational artifacts—review them carefully before sharing or running them in new environments.

Prefer least-privilege execution environments for tooling.
Sanitize secrets (API keys/tokens) before exporting or publishing configurations.
Pin tool versions where reproducibility matters.

Sponsored by the-street.xyz, a private forum for cybersecurity, threat intelligence, and cipherpunk culture.

Ready to explore Reckoning?

Browse the repository, read the docs, and start composing workflows.

View on GitHub Back to top