docs: add contributing guide and stargazers

Author: GangGreenTemperTatum

README.md

@@ -48,6 +48,9 @@ The AIRTBench agent is designed to evaluate the autonomous red teaming capabilit
   - [Dataset](#dataset)
   - [Citation](#citation)
   - [Model requests](#model-requests)
+  - [🤝 Contributing](#-contributing)
+  - [🔐 Security](#-security)
+  - [⭐ Star History](#-star-history)
 
 ## Agent Harness Construction
 
@@ -135,4 +138,20 @@ If you find our work helpful, please use the following citations.
 
 ## Model requests
 
-If you know of a model that may be interesting to analyze, but do not have the resources to run it yourself, feel free to open a feature request via a GitHub issue.
+If you know of a model that may be interesting to analyze, but do not have the resources to run it yourself, feel free to open a feature request via a GitHub issue.
+
+## 🤝 Contributing
+
+Forks and contributions are welcome! Please see our [Contributing Guide](docs/contributing.md).
+
+## 🔐 Security
+
+See our [Security Policy](SECURITY.md) for reporting vulnerabilities.
+
+## ⭐ Star History
+
+[![GitHub stars](https://img.shields.io/github/stars/dreadnode/AIRTBench-Code?style=social)](https://github.com/dreadnode/AIRTBench-Code/stargazers)
+
+By watching the repo, you can also be notified of any upcoming releases.
+
+[![Star history graph](https://api.star-history.com/svg?repos=dreadnode/AIRTBench-Code&type=Date)](https://star-history.com/#dreadnode/AIRTBench-Code&Date)

docs/contributing.md

@@ -0,0 +1,140 @@
+# Contributing Guide
+
+Thank you for your interest in contributing to this project! This guide will
+help you get started with contributing effectively.
+
+## Getting Started
+
+1. Fork the repository and clone your fork:
+
+   ```bash
+   gh repo clone dreadnode/AIRTBench-Code
+   cd AIRTBench-Code
+   ```
+
+1. Set up your development environment with your preferred package manager:
+
+   ```bash
+   # Using pip
+   python -m venv .venv
+   source .venv/bin/activate  # On Windows: .venv\Scripts\activate
+   pip install -r requirements.txt
+
+   # Using uv
+   uv venv
+   source .venv/bin/activate
+   uv pip install -r requirements.txt
+
+   # Using poetry
+   poetry install
+   ```
+
+1. Install and configure pre-commit hooks:
+
+   ```bash
+   pre-commit install
+   ```
+
+1. Create a new branch for your contribution:
+
+   ```bash
+   git checkout -b your-feature-name
+   ```
+
+## Development Process
+
+### Code Quality Checks
+
+Before submitting your changes, ensure all quality checks pass:
+
+```bash
+# Run all checks at once
+task check
+
+# Or run individual checks:
+task format  # Code formatting with Black
+task lint    # Linting with Ruff
+task types   # Type checking with mypy
+task test    # Run tests with pytest
+```
+
+The pre-commit hooks will automatically run most checks when you commit changes.
+
+### Documentation
+
+- Add documentation for new features in the `docs/` directory
+- Update existing documentation to reflect your changes
+
+### Commit Messages
+
+Follow [Conventional Commits](https://www.conventionalcommits.org/) for your
+commit messages:
+
+```bash
+# Format: <type>: <description>
+feat: add new template feature
+fix: resolve issue with pytest config
+docs: improve setup instructions
+ci: update GitHub Actions workflow
+```
+
+Common types: `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `ci`, `chore`
+
+## Pull Request Process
+
+1. Update your branch with the latest changes:
+
+   ```bash
+   git fetch origin
+   git rebase origin/main
+   ```
+
+1. Push your changes:
+
+   ```bash
+   git push origin your-feature-name
+   ```
+
+1. Create a pull request with:
+
+   - Clear, descriptive title following conventional commits
+   - Detailed description of changes
+   - Links to related issues
+   - Screenshots for UI changes (if applicable)
+   - Documentation updates
+   - Template updates (if required)
+
+1. Address any review feedback and update your PR
+
+## Code Standards
+
+- Follow the existing code style (enforced by Black and Ruff)
+- Maintain type hints and add new ones for your code
+- Write clear docstrings for new functions and classes
+- Add tests for new features or bug fixes
+- Keep changes focused and atomic
+- Update example code if needed
+
+## Project Structure
+
+When adding new features, follow the project structure:
+
+```bash
+.
+├── docs/              # Documentation
+├── examples/          # Usage examples
+├── tests/             # Test suite
+└── pyproject.toml     # Project configuration
+```
+
+## Getting Help
+
+- Check existing issues and pull requests
+- Open a new issue for:
+
+  1. Bug reports
+  1. Feature requests
+  1. Questions about the template
+  1. Contributing questions
+
+We aim to respond to all issues promptly.