red-team-bundler

To bundle source files for an external red team security review, you need a structured auditor prompt and a manifest. This Skill automates that process by isolating relevant code, generating prompt.md, and packaging everything into a Markdown payload or ZIP archive.

A red team security bundle includes a focused auditor prompt defining engagement rules and threat models, a file-manifest.json with the prompt listed first, and the isolated source code files gathered into a single shareable Markdown payload or ZIP archive.

You generate an auditor prompt and manifest by creating a temporary workspace where the Skill writes prompt.md encoding red team rules, then builds file-manifest.json to assemble the relevant project files for deterministic packaging.

Yes, you can output a ZIP archive instead of Markdown for your security review payload. The Skill uses core Context Bundler scripts to produce your bundled files and prompt in either a single Markdown artifact or a ZIP format.

Preparing a red team bundle does not require external dependencies. The Skill operates independently to create the temporary workspace, write the prompt, and use Context Bundler scripts to package the final payload.

You should use an automated red team bundler instead of manual file collection when security teams need a structured, ready-to-share payload for a new feature. It ensures deterministic packaging and enforces a strict auditor prompt at the top of the bundle.