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.
npx skills add zgbrenner/agentcounsel --skill executory-contract-assumption-rejection-checklistgit clone --depth 1 https://github.com/zgbrenner/agentcounselWrote 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.
[](https://agentmods.dev/skills/zgbrenner/agentcounsel/executory-contract-assumption-rejection-checklist)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/executory-contract-assumption-rejection-checklist"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/executory-contract-assumption-rejection-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.
<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/executory-contract-assumption-rejection-checklist"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/executory-contract-assumption-rejection-checklist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00038 | $0.01518 |
| Opus 5 | $0.00019 | $0.00759 |
| Sonnet 5 | $0.00008 | $0.00304 |
| Haiku 4.5 | $0.00004 | $0.00152 |
Grade A, and why
Executory Contract Assumption Rejection 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executory Contract Assumption Rejection Checklist
Purpose
Organize executory contract and unexpired lease facts into a source-cited contract status table, a cure/default tracker, and an assumption/rejection issue list, so a qualified attorney can evaluate assumption, rejection, and assignment. This skill organizes facts and spots issues; it never concludes whether a contract is executory or whether it may be assumed, rejected, or assigned. It produces draft legal work product for attorney review — not legal advice.
Use When
- A debtor or a counterparty needs the facts of an executory contract or unexpired lease organized for an attorney's assumption/rejection analysis.
- A team needs cure amounts, defaults, assignment rights, and consent issues captured with sources.
- A contract portfolio must be triaged before an attorney evaluates assumption or rejection.
Required Inputs
- Contract or lease identity, and the debtor and counterparty roles.
- The user's party role (debtor-side, counterparty, buyer-side, or other).
- Cure amounts as provided (recorded as stated, never computed or confirmed).
- Defaults asserted and notice history, with source references.
- Assignment rights, anti-assignment or change-of-control language, and any consent issues, with clause citations.
- Critical-vendor status if raised (recorded as raised, never confirmed).
- Assumption or rejection status, if any, and any related deadlines echoed and
marked
[deadline verification required]. - Business impact as the user describes it.
- Source documents with citations to contract clauses, notices, or pages.
If the contract identity, the party roles, or the contract text is missing,
record it as not provided and return the missing-information list first.
Do Not Use When
- The request is to conclude whether a contract or lease is executory or unexpired.
- The request is to conclude whether it may be assumed, rejected, or assigned, or to determine a cure amount.
- The request is for legal advice or a deadline calculation.
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.
- 11d ago First seen · 145 lines · 38 tokens per session scan A cb73b066c038
Executory Contract Assumption Rejection Checklist is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 1,518 once invoked, about $0.0002 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.
Other skills, from other repositories
legaltech-expert
Expert in legal technology: contract lifecycle management, e-discovery, AI-assisted legal research, case and matter management, document automation, and compliance tooling. Use when the user mentions legal case or matter management, e-discovery and legal holds, CLM or contract review and obligation tracking, legal…
cross-check-legal-advice
How to safely use AI for legal issue-spotting, contract clause translation, and preparing targeted questions for licensed legal counsel.
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.
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.
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.
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…