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 distribution-restraints-reviewgit 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/distribution-restraints-review)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/distribution-restraints-review"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/distribution-restraints-review/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/distribution-restraints-review"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/distribution-restraints-review.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.00089 | $0.02554 |
| Opus 5 | $0.00044 | $0.01277 |
| Sonnet 5 | $0.00018 | $0.00511 |
| Haiku 4.5 | $0.00009 | $0.00255 |
Grade A, and why
Distribution Restraints Review 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Distribution Restraints Review
Purpose
Review distribution, dealer, franchise, reseller, and marketplace arrangements for vertical-restraint exposure — RPM and MAP programs, territory and customer restrictions, online-sales and marketplace limits, dual pricing, selective-distribution criteria, exclusivity, and tying — and organize a restraint inventory with per-jurisdiction character flags, ancillarity and rationale notes, and separate callouts for active-enforcement areas such as online-sales bans and dual pricing. The deliverable is draft legal work product for attorney review: restraint character (hardcore vs. rule-of-reason vs. mixed) is recorded as a question for counsel per jurisdiction, and the skill never concludes enforceability, legality, or market power.
Use When
- Sales or channel teams propose a MAP policy, a minimum-price program, or consequences for discounting dealers, and counsel needs it screened before rollout.
- A distribution or dealer agreement restricts online sales, bans specified marketplaces, or applies different wholesale prices to online vs. offline volume.
- A supplier wants to assign exclusive territories or customer classes to distributors, or to tighten selective-distribution criteria that may exclude online-only or discount dealers.
- A dealer complaint, termination dispute, or threat letter puts an existing restraint program under scrutiny.
- The company sells direct and through dealers in the same market, and the dual-distribution information flows and channel protections need review.
- An existing distribution program is expanding into new jurisdictions where the same restraints may be treated differently.
Required Inputs
- Jurisdiction(s) of competitive effect — every country and, where relevant, state/province where the distribution arrangement operates or has effects, or
[verify jurisdiction]. Note that distribution rules vary substantially across jurisdictions. - Distribution structure — direct sales, distributors, dealers, resellers, online marketplaces, agents, franchise, or hybrid. Mark unknowns
unknown/not found/not provided/ambiguous. - Restraints in scope — MAP (minimum advertised price), RPM (resale price maintenance), territory restrictions, customer restrictions, online-sales restrictions, marketplace bans, dual pricing, selective-distribution criteria, tying or bundling, exclusivity (single- or multi-brand), requirements contracts, non-compete during/after, termination provisions.
- Brand and channel context — sole supplier or one of many; branded vs. private-label; service-intensive vs. commodity; brand reputation considerations; channel-conflict facts.
- Buyer-side context — buyer size, buyer overlap, buyer competitors, large-account carveouts, buyer-induced restraints.
- Vertical market position — user-supplied supplier-side share, user-supplied buyer-side share. Never invented.
- Business rationale — service quality, free-rider concerns, brand image, retailer investment incentives, anti-counterfeiting, safety, regulatory.
- Documents and source anchors — distribution agreement(s), policies, MAP letters, marketplace policies, dealer manuals, communications.
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.
- 12d ago First seen · 123 lines · 89 tokens per session scan A eedd10529d5f
Distribution Restraints Review is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 2,554 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.