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 acquisition-diligence-request-listgit 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/acquisition-diligence-request-list)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/acquisition-diligence-request-list"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/acquisition-diligence-request-list/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/acquisition-diligence-request-list"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/acquisition-diligence-request-list.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.00036 | $0.02552 |
| Opus 5 | $0.00018 | $0.01276 |
| Sonnet 5 | $0.00007 | $0.00510 |
| Haiku 4.5 | $0.00004 | $0.00255 |
Grade A, and why
Acquisition Diligence Request List 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 7d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Acquisition Diligence Request List
Purpose
Generate a tailored due-diligence request list for a merger, acquisition, or strategic investment — the list of documents, data, and information a buyer asks the target to produce, or that a seller prepares to populate a data room. The list is organized by workstream and shaped to the deal type, the industry, the target profile, the transaction stage, and the known risks.
This skill produces draft work product for attorney review only. It is not legal advice and it is not a statement of what diligence the law or a duty of care requires. The reviewing attorney decides the scope of diligence, what the list must add or drop, and when the diligence is sufficient.
Use When
- A user asks to "build a diligence request list," "draft a due-diligence checklist," "what should we ask the target for," or "prepare our data-room request list."
- A buyer-side deal team needs a tailored diligence request list before or during diligence on an acquisition, merger, asset purchase, stock purchase, or strategic investment.
- A seller-side or company-side team needs a request list to anticipate buyer diligence and prepare a data room.
Required Inputs
- The deal type — for example a stock purchase, asset purchase, merger, membership-interest purchase, carve-out, acqui-hire, roll-up, or minority investment.
- The industry and the target profile — what the target does, its approximate size, structure, and any distinguishing features (regulated business, consumer data, manufacturing footprint, software product, and so on).
- The side the list is for — buyer-side or seller-side (or company-side, investor-side, or target-side).
- The transaction stage — for example pre-LOI, post-LOI confirmatory diligence, or pre-signing.
- Known risks or focus areas — anything the team already wants to probe.
- Jurisdiction — the jurisdiction(s) of the target and the deal, as the user states them, or flagged as unknown.
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.
- 7d ago First seen · 229 lines · 36 tokens per session scan A 9ef55b57a47b
Acquisition Diligence Request List is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 2,552 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-09-03.
Other skills, from other repositories
performance-management
Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance. Use this to design or fix a review process, run calibration, write or coach on feedback, address sustained underperformance, or work out why reviews consume weeks and change nothing.
vendor-evaluation
Evaluate, select, and contract with vendors and SaaS tools. Use this skill when comparing alternatives, running an RFP, scoring vendors against criteria, negotiating contracts, planning a switch, or assessing a vendor's risk. Triggers on vendor evaluation, RFP, vendor selection, build vs buy, SaaS evaluation, vendor…
delay-analysis
Analyze construction schedule delays for claims and recovery. Perform time impact analysis, identify delay causes, calculate damages, and document for disputes.
change-order-manager
Manage construction change orders from request to approval. Track costs, schedule impacts, and maintain audit trail for dispute prevention.
claims-documentation
Document construction claims for disputes and recovery. Compile evidence, calculate damages, track notice requirements, and prepare claim packages.
compliance-tracker
Track regulatory compliance for construction projects. Monitor permits, certifications, inspections, and regulatory requirements with automated alerts and reporting.