grendel-redteam 0.1.0__tar.gz

grendel_redteam-0.1.0/.claude/agents/plan-reviewer.md

@@ -0,0 +1,21 @@
+---
+name: plan-reviewer
+description: Reviews and strengthens an implementation plan before any code is written. Use proactively right after a plan.md is created for a phase, before implementation starts.
+tools: Read, Grep, Glob
+model: sonnet
+---
+
+You are a senior technical architect. You do NOT write code — you only review plans.
+
+Read the current phase's `spec.md` and `plan.md`. Evaluate the plan for:
+- missing steps or hidden dependencies
+- risky assumptions
+- untested edge cases
+- conflicts with the existing codebase
+- whether each milestone has a clear, verifiable acceptance checkpoint
+
+Append your findings to the phase's `plan.md` under a `## Plan review` section as a
+numbered, concrete list of improvements. Then end your message with exactly one line:
+
+- `STATUS: PASS` — the plan is solid and ready to implement, or
+- `STATUS: REVISE` — followed by the top fixes that must be applied first.

grendel_redteam-0.1.0/.claude/agents/reviewer.md

@@ -0,0 +1,20 @@
+---
+name: reviewer
+description: Independent code reviewer. Use at each milestone within a phase, after a chunk of the plan is implemented. Reviews the diff against the phase plan and reports PASS or BLOCKING. Use immediately after writing or modifying code at a checkpoint.
+tools: Read, Grep, Glob, Bash
+model: sonnet
+---
+
+You review code you did NOT write. Your job is independent verification, not implementation.
+
+1. Read the current phase's `plan.md` to understand what this milestone was supposed to deliver.
+2. Inspect the recent changes (use `git diff` and read the touched files).
+3. Check: correctness, security, error handling, and adherence to the plan.
+
+Write your findings to `phases/<current-phase>/review.md` as a numbered, actionable list.
+End that file (and your message) with exactly one line:
+
+- `STATUS: PASS` — no blocking issues, safe to continue, or
+- `STATUS: BLOCKING` — followed by the issues that must be fixed before proceeding.
+
+Do NOT edit application code. Only write the review file.

grendel_redteam-0.1.0/.claude/agents/tester.md

@@ -0,0 +1,20 @@
+---
+name: tester
+description: Runs the test suite for the current phase and reports results. Use at each milestone, after the reviewer, and before a phase is marked done.
+tools: Read, Grep, Glob, Bash
+model: sonnet
+---
+
+You run tests and report results. You do NOT fix code.
+
+1. Run the project's test command (see `.claude/scripts/gate.sh` for the configured command,
+   or the project README). Scope it to the current phase's area when possible.
+2. Capture failures with their error messages — not the full noisy output.
+
+Write a concise summary to `phases/<current-phase>/test-report.md` and end that file
+(and your message) with exactly one line:
+
+- `STATUS: PASS` — all tests green, or
+- `STATUS: BLOCKING` — followed by the list of failing tests and their key errors.
+
+Do NOT modify application code. Only run tests and report.

grendel_redteam-0.1.0/.claude/scripts/gate.sh

@@ -0,0 +1,36 @@
+#!/usr/bin/env bash
+# PostToolUse gate — runs after every Edit / Write / MultiEdit.
+#
+# Keep this FAST: lint / format-check / typecheck only. The FULL test suite
+# is run by the `tester` agent at milestones, not here, so editing stays quick.
+#
+# Exit code 2 = block and show the message to Claude so it fixes the issue.
+
+set -uo pipefail
+
+# ===================== CONFIGURE THIS FOR YOUR STACK =====================
+# Examples:
+#   Python:     QUICK_CMD="ruff check . && pyright"
+#   Node/TS:    QUICK_CMD="npm run lint && npm run typecheck"
+#   Go:         QUICK_CMD="gofmt -l . && go vet ./..."
+#   Rust:       QUICK_CMD="cargo fmt --check && cargo clippy -- -D warnings"
+# Skip a tool until it's installed (e.g. before the Phase 1 venv exists).
+QUICK_CMD='ok=0
+if command -v ruff   >/dev/null 2>&1; then ruff check . || ok=1; fi
+if command -v pyright >/dev/null 2>&1; then pyright    || ok=1; fi
+exit $ok'
+# ========================================================================
+
+out="$(bash -c "$QUICK_CMD" 2>&1)"
+status=$?
+
+if [ "$status" -ne 0 ]; then
+  {
+    echo "Quick-check failed. Fix these before continuing:"
+    echo "----------------------------------------------"
+    echo "$out"
+  } >&2
+  exit 2
+fi
+
+exit 0

grendel_redteam-0.1.0/.claude/settings.json

@@ -0,0 +1,15 @@
+{
+  "hooks": {
+    "PostToolUse": [
+      {
+        "matcher": "Edit|Write|MultiEdit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "./.claude/scripts/gate.sh"
+          }
+        ]
+      }
+    ]
+  }
+}

grendel_redteam-0.1.0/.claude/skills/phase/SKILL.md

@@ -0,0 +1,48 @@
+---
+name: phase
+description: Drives a single project phase end-to-end through the harness loop. Use this whenever the user says "/phase", "start phase N", "run the next phase", or wants to take one phase of the ROADMAP from spec to verified completion. Always use this for phase-by-phase delivery, even if the user does not say the word "phase" explicitly but is clearly working through the roadmap.
+---
+
+# Phase driver
+
+Runs one phase of `ROADMAP.md` through the full loop:
+spec → plan → reviewed plan → implementation → milestone verification → done.
+
+## Input
+
+The phase number (e.g. "phase 03"). If not given, read `ROADMAP.md` and pick the
+first phase whose `phases/phase-NN/` folder has no passing `test-report.md`.
+
+## Steps
+
+1. **Set up the phase folder.** Create `phases/phase-NN/` if it does not exist.
+
+2. **Spec.** Use the `brainstorming` skill to turn this phase's `ROADMAP.md` entry
+   into a detailed spec. Save it as `phases/phase-NN/spec.md`.
+
+3. **Plan.** Use the `writing-plans` skill to turn `spec.md` into an implementation
+   plan. Save it as `phases/phase-NN/plan.md`. The plan MUST break the work into
+   numbered milestones, each ending in a verifiable checkpoint.
+
+4. **Review the plan.** Invoke the `plan-reviewer` agent. If it returns
+   `STATUS: REVISE`, apply the fixes to `plan.md` and re-run it until `STATUS: PASS`.
+
+5. **Implement, milestone by milestone.** For each milestone in `plan.md`:
+   1. Implement that milestone's work.
+   2. At the checkpoint, invoke the `reviewer` agent, then the `tester` agent.
+   3. If either returns `STATUS: BLOCKING`, fix the issues and repeat step 5.2
+      until BOTH return `STATUS: PASS`. Only then move to the next milestone.
+
+6. **Close the phase.** When every milestone passes, confirm that `review.md` and
+   `test-report.md` both end in `STATUS: PASS`, then summarize what shipped and stop.
+   Do NOT start the next phase automatically — wait for the user to review and say go.
+
+## Notes
+
+- A `PostToolUse` gate hook runs a quick lint/typecheck after every edit. Treat its
+  failures as must-fix before continuing.
+- Keep all phase state in the `phases/phase-NN/` files (spec, plan, review, test-report)
+  so the working context stays small and later phases can read earlier ones.
+- To run a phase autonomously to completion, the user can pair this with:
+  `/goal Complete phase NN per phases/phase-NN/plan.md, until review.md and
+  test-report.md both say STATUS: PASS.`

grendel_redteam-0.1.0/.claude/skills/run-all/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: run-all
+description: Runs every phase in ROADMAP.md sequentially through the full phase loop until the whole project is built. Use whenever the user wants to build the entire project end-to-end autonomously, e.g. "run all phases", "build the whole thing", "do the full roadmap". Always stop at the first phase that cannot pass.
+---
+
+# Run all phases
+
+Builds the entire project by running each phase of `ROADMAP.md` in order through
+the `phase` skill, with a hard stop on any phase that cannot reach passing status.
+
+## Steps
+
+1. Read `ROADMAP.md` and list every phase in order.
+
+2. Determine the starting phase: the first phase NN whose `phases/phase-NN/`
+   folder does NOT contain a `test-report.md` ending in `STATUS: PASS`.
+   (This makes the run resumable — already-finished phases are skipped.)
+
+3. For each phase NN from the start, one at a time:
+   1. Run the `phase` skill for phase NN, fully:
+      spec → plan → `plan-reviewer` → implement milestone by milestone →
+      `reviewer` + `tester` at each checkpoint, until BOTH report `STATUS: PASS`.
+   2. Confirm `phases/phase-NN/review.md` AND `phases/phase-NN/test-report.md`
+      both end in `STATUS: PASS`.
+   3. Append one line to `PROGRESS.md`: `phase NN: DONE` (with a one-line summary).
+   4. Only then move to phase NN+1.
+
+4. **Hard stop on trouble.** If a phase cannot reach `STATUS: PASS` after a
+   reasonable number of fix attempts, STOP. Do NOT skip ahead or start the next
+   phase. Append `phase NN: BLOCKED — <reason>` to `PROGRESS.md` and report to
+   the user what is blocking and what you tried.
+
+5. When every phase is `DONE`, append `ALL PHASES COMPLETE` to `PROGRESS.md`
+   and stop with a summary.
+
+## Rules
+
+- Never start phase NN+1 until phase NN is `DONE`. Phases are sequential and
+  later phases may depend on earlier ones.
+- Never weaken a checkpoint to make it pass. A real `STATUS: PASS` from an
+  independent `reviewer` and `tester` is the only way forward.
+- Keep all state in `phases/phase-NN/` files and `PROGRESS.md` so context stays
+  small and the run is auditable.

grendel_redteam-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,51 @@
+name: release
+
+# Build the wheel and publish to PyPI when a version tag (v*) is pushed.
+# Uses PyPI Trusted Publishing (OIDC) — no API token secret needed. Before the first release,
+# configure a Trusted Publisher on PyPI for the `grendel-redteam` project pointing at this repo +
+# the `pypi` environment (https://docs.pypi.org/trusted-publishers/).
+
+on:
+  push:
+    tags:
+      - "v*"
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: pip install -e ".[dev]"
+      - run: ruff check src tests
+      - run: pytest -q
+
+  build:
+    needs: test
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: pip install build
+      - run: python -m build
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write  # required for Trusted Publishing
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

grendel_redteam-0.1.0/.gitignore

@@ -0,0 +1,23 @@
+# Secrets — never commit
+.env
+.env.*
+*.key
+grendel.local.yaml
+
+# Per-user working config at the repo root (has local paths/targets); the tracked example is
+# examples/grendel.example.yaml.
+/grendel.yaml
+
+__pycache__/
+*.egg-info/
+.pytest_cache/
+.ruff_cache/
+runs/
+venv/
+.venv/
+build/
+dist/
+
+# Imported open-corpus catalog — regenerated with one `grendel import` (not committed;
+# may include toxicity prompts). Wire it via catalog.pack_dirs / --pack-dir.
+catalog/

grendel_redteam-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.