Gun Jumping Clean Team Checklist

Gun Jumping Clean Team Checklist is a skill for Claude Code, Codex from zgbrenner/agentcounsel. It costs 91 tokens per session (2,720 once invoked), scanned A, original, MIT.

A pre-closing merger review checklist for deals that have been signed but are still awaiting regulatory approval. It compares planned conduct and information sharing with the purchase agreement and clean-team controls; it does not decide whether conduct is legally compliant.

In plain words
What is it for?
Documenting covenants, consent rights, pricing or customer discussions, clean-team arrangements, and integration-planning guardrails during the waiting period.
Why use it?
It helps identify sensitive information flows, joint actions, and departures from agreed safeguards before lawyers review them.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Documenting covenants, consent rights, pricing or customer discussions, clean-team arrangements, and integration-planning guardrails during the waiting period.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zgbrenner/agentcounsel/gun-jumping-clean-team-checklist
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add zgbrenner/agentcounsel --skill gun-jumping-clean-team-checklist
Clone the repo
git clone --depth 1 https://github.com/zgbrenner/agentcounsel

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for Gun Jumping Clean Team Checklist

README.md
[![agentmods](https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/gun-jumping-clean-team-checklist/github.svg)](https://agentmods.dev/skills/zgbrenner/agentcounsel/gun-jumping-clean-team-checklist)
Your own site
<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/gun-jumping-clean-team-checklist"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/gun-jumping-clean-team-checklist/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for Gun Jumping Clean Team Checklist

Your own site · 80×15
<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/gun-jumping-clean-team-checklist"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/gun-jumping-clean-team-checklist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 91 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,720 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00091 $0.02720
Opus 5 $0.00046 $0.01360
Sonnet 5 $0.00018 $0.00544
Haiku 4.5 $0.00009 $0.00272

Measured 12d ago against content hash 283ef375183e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

Gun Jumping Clean Team Checklist scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/antitrust-competition/gun-jumping-clean-team-checklist/SKILL.md · 126 lines

How it starts

The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Gun Jumping Clean Team Checklist

Purpose

Check pre-closing conduct between signed-but-not-closed merger parties against the purchase agreement's covenants and gun-jumping discipline: inventory the pre-closing covenants and consent rights, log actual conduct against them, map every information flow with its control posture, test the clean-team design, and build the integration-planning guardrail list. The deliverable is a draft for attorney review — every deviation, high-sensitivity information flow, joint communication, and guardrail item is an escalation trigger for counsel, and the skill never concludes HSR/Article 7 compliance or approves any pre-closing step.

Use When

  • The deal team wants to start integration planning, align pricing, or make joint customer calls before closing, and counsel needs the guardrails documented.
  • A signed deal is in the HSR or EU waiting period and someone asks what the parties may and may not do until clearance.
  • Diligence or integration workstreams are already exchanging pricing, customer, or capacity data, and the flows need to be logged against the clean-team protocol.
  • Counsel needs the purchase agreement's consent rights and operate-in-ordinary-course covenant screened for acquirer-control overreach.
  • A joint announcement, co-branded customer letter, or joint sales call is proposed — or has already happened — between signing and closing.
  • An extended review (second request, phase II) means pre-closing conduct discipline must hold for months and needs a documented checklist.

Required Inputs

  • Jurisdiction(s) of competitive effect — every country and, where relevant, state/province where the parties operate, or [verify jurisdiction]. Gun-jumping rules apply per regime (US HSR/section 1; EU Article 7 standstill / Article 101; UK / China / others).
  • Transaction structure and parties — acquirer, target, ultimate parents, sister entities; consideration mix; concurrent or related transactions. Mark unknowns unknown/not found/not provided/ambiguous.
  • Parties' competitive posture — actual / potential / no competition, per product market.
  • Procedural posture — signing date, target closing date [deadline verification required], HSR status, second-request status, non-US filing status.
  • Pre-closing covenants in the purchase agreement — operate-in-ordinary-course covenant; affirmative covenants; restrictive covenants; consent rights and thresholds; integration-planning carveouts.
  • Decision-making touchpoints — pricing, output, capacity, hiring/firing, customer/supplier contracts, capex, M&A pipeline, strategic positioning.
  • Information-sharing posture to date — what has been shared, by whom, with whom, under what controls. Cross-references to information-sharing-clean-team-review welcome.
  • Clean-team composition — counsel, outside advisors (economists, consultants), designated business individuals (with role and scope), exclusions.
  • Integration-planning activity to date — meetings held, attendees, topics, outputs, controls in place.
  • External communications to date — customer, vendor, and employee communications by either party that reference the deal or each other.
  • Documents and source anchors — purchase agreement, clean-team agreement, integration-planning documents, board materials, deal-team communications.

Read the full file on GitHub · 126 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 126 lines · 91 tokens per session scan A 283ef375183e

Subscribe to this mod's changes

Gun Jumping Clean Team Checklist is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 91 tokens to every session and 2,720 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

legal-research

A legal research skill for finding and analysing laws and court cases, including similar cases. It requires access to a reliable legal research database before producing a formal report.

code-lawyer/Legal-Agent-Skills · 144 tokens

document-fill

A document-filling assistant that uses a supplied template and case files to fill in forms, contracts, or legal documents. It also reports where each filled value came from and which details are missing.

code-lawyer/Legal-Agent-Skills · 61 tokens

contract-review

A contract-review workflow for agreements governed by Chinese law, United States law, or both. It examines clauses one by one and produces a list of legal-risk questions, with an optional marked-up Word document.

code-lawyer/Legal-Agent-Skills · 86 tokens

fedramp

Expert guidance for FedRAMP certification and compliance under CR26 (FedRAMP Consolidated Rules for 2026). Use this skill whenever a user asks about FedRAMP authorization, ATO (Authority to Operate), cloud security for federal government, NIST SP 800-53 controls, CSP compliance, or any of the core FedRAMP document…

Sushegaad/Claude-Skills-Governance-Risk-and-Compliance · 236 tokens

eu-cra

Expert EU Cyber Resilience Act (CRA) advisor for Regulation (EU) 2024/2847 — mandatory cybersecurity and vulnerability handling requirements for all products with digital elements (PDEs) sold in the EU. Use this skill for gap analysis, product classification (Default / Class I / Class II), conformity assessment route…

Sushegaad/Claude-Skills-Governance-Risk-and-Compliance · 133 tokens

aenderungsvorbehalt-308

Für Änderungsvorbehalt 308: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.

Klotzkette/claude-fuer-deutsches-recht · 41 tokens