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 merger-antitrust-issue-spottergit 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/merger-antitrust-issue-spotter)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/merger-antitrust-issue-spotter"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/merger-antitrust-issue-spotter/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/merger-antitrust-issue-spotter"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/merger-antitrust-issue-spotter.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.00086 | $0.03015 |
| Opus 5 | $0.00043 | $0.01507 |
| Sonnet 5 | $0.00017 | $0.00603 |
| Haiku 4.5 | $0.00009 | $0.00301 |
Grade A, and why
Merger Antitrust Issue Spotter 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merger Antitrust Issue Spotter
Purpose
Issue-spot the antitrust dimensions of a contemplated or signed transaction and organize the facts counsel needs: horizontal-overlap and vertical-relationship matrices built from user-supplied market facts, potential/nascent-competition and adjacent-overlap flags (data, IP, labor markets, innovation pipelines), a per-regime filing-question list, a diligence request list, and pre-closing integration guardrails. All of it is draft legal work product for attorney review — market definition, reportability, and competitive effects remain attorney determinations, and the skill never defines a market or predicts clearance.
Use When
- A deal team has an LOI or term sheet with a competitor, supplier, customer, or adjacent player, and counsel needs the antitrust issues mapped before signing.
- Diligence has begun and the overlaps — horizontal, vertical, potential-competition, data/IP/labor — need to be organized from the deal documents into matrices.
- The board or deal lead asks in which jurisdictions the transaction might need to be filed, and counsel needs the questions framed per regime (HSR, EU EUMR, UK CMA, China SAMR, Brazil CADE, others).
- Counsel needs a diligence request list targeted at the antitrust workstream — customer lists, win/loss data, internal share estimates, deal-rationale documents.
- The parties are starting pre-closing integration planning, and the issue-spotter needs to feed the gun-jumping and information-sharing reviews.
- A minority investment or JV raises partial-ownership and governance questions alongside a competitive overlap.
Required Inputs
- Jurisdiction(s) of competitive effect — every country and, where relevant, state/province where the parties sell, source, or employ. Use
[verify jurisdiction]if unknown. Note that the antitrust analysis follows the markets, not the parties' headquarters. - Transaction structure — asset / stock / statutory merger / joint venture / minority investment; consideration mix; ultimate parents on each side; sister entities and bolt-ons; any concurrent transactions with related counterparties. Mark unknowns
unknown/not found/not provided/ambiguous. - Parties and competitive posture — acquirer, target, and each entity's role on each product market: horizontal competitor, vertical supplier/customer, potential competitor, nascent competitor, or none. Include any prior or contemplated competitor relationship (collaborations, JVs, licensing).
- Product and geographic markets — the user's preliminary view of each product line in scope, the geographic footprint of each, and customer-substitution evidence the user has. Market definition itself is for the attorney; the skill organizes the facts.
- Market structure facts (if supplied) — user-supplied shares, HHI, entry conditions, customer concentration, switching costs, capacity. Never invented; never computed from incomplete data.
- Adjacent overlaps — data assets, IP portfolios, labor-market overlap (especially specialized roles), and innovation pipelines.
- Pre-closing conduct to date — competitively sensitive information shared, integration-planning meetings held, clean-team scope, pricing or commercial decisions touched by both sides, customer/supplier communications.
- Procedural posture and timing — signing status, HSR filing status, non-US filing status (EU, UK, China, Brazil, others as applicable), second-request / phase II status, target closing date. All dates
[deadline verification required]. - Documents reviewed and source anchors — purchase agreement, deal-team emails, board materials, integration plans, CIM/teaser, HSR drafts, customer/supplier lists. Every extracted fact cites the document and page/section.
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 · 131 lines · 86 tokens per session scan A cb8cc18af692
Merger Antitrust Issue Spotter is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 3,015 once invoked, about $0.0004 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
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…
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…
aenderungsvorbehalt-308
Für Änderungsvorbehalt 308: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.