Each ostk Command is defined in a file in the _OffSecToolKit/ folder named as <tool name>.md, such file consists only of a YAML front matter which describes the command and its attributes.
The full syntax is the following:
---
description: Description of what the command does.
Command Reference:
Target IP: 10.10.10.1
Domain: test.local
Username: john
Password: password123
command: |
put command here
items:
- ITEM
- ITEM
...
services:
- SERVICE
...
OS:
- OS
...
phases:
- PHASE
references:
- LINK
- LINK
...
---
Where ITEM is one of the values described in the _data/items.yml file, SERVICE is one of the values described in the _data/services.yml file, OS is one of the values described in the _data/OS.yml file, PHASE is one of the values described in the _data/phases.yml file, and LINK is a link to download the related tool for that command as well as links to any other relevant information about what the command is doing.
Feel free to use any file in the _OffSecToolKit/ folder as an example.
I accept commands that run on either Linux or Windows, just as long as they target Windows machines (this is a Windows/AD cheat sheet after all).
Before sending a pull request of a new command, ensure the following:
john, password123, test.local and 10.10.10.1 respectively.references.Pull requests adding new items in _data/items.yml, services in _data/services.yml, OS in _data/OS.yml, or phases in _data/phases.yml are allowed and subjected to project maintainers vetting.