8.7 Tool Repository Curation

What you're building: A public GitHub presence that demonstrates coding ability through original tools — not forks, not scripts, but actual tools with documentation, a demo, and real-world utility that other practitioners will actually use.

Build and maintain a public GitHub repository of original offensive tools that demonstrates coding ability and domain expertise.

Technique: Open Source Project Management

Tools/Templates: GitHub, README.md, MIT License, asciinema

Procedure:

# [Tool Name] — [One-line description]
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)

## Description
[2-3 sentences: what the tool does, the problem it solves, and why existing tools don't solve it.]

## Installation
```bash
git clone https://github.com/user/tool
pip install -r requirements.txt
```

## Usage
```bash
python tool.py --target 10.10.10.10 --attack kerberoast --output results.json
```

## Demo
![Terminal demo GIF — keep under 30 seconds]

## Why This Tool Exists
[One paragraph: what gap in the existing tooling does this fill?
E.g., "Existing tools require admin rights for X. This tool achieves the same result from a low-privileged context by ..."]

## License
MIT

Documentation Standards

Docstrings: Use Google-style docstrings for all functions — single source of truth for what each function does and what it returns
Comments: Explain the why, not the what. "# Use APC injection here because CreateRemoteThread is hooked" > "# inject the shellcode"
CHANGELOG.md: Maintain following "Keep a Changelog" format — versions, dates, Added/Changed/Fixed sections
Sample Output: Provide a sample.log or output.json for users to test parsing or understand output format without running the tool

Demo Artifact Requirements

GIFs: Use asciinema for terminal demos. Convert to GIF with agg. Keep under 30 seconds.
Screenshots: High resolution, cropped to relevant content, clearly annotated with arrows or boxes
Infrastructure: If your tool requires a specific lab setup, provide a docker-compose.yml for instant reproduction

NOTE: A clean README with a working demo GIF is more likely to get stars and attract employers than a repo with better code and no documentation. The README is the product for open source tools.

Part of Pillar 8: Reporting & Portfolio Development.