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 open-source-license-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/open-source-license-review)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/open-source-license-review"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/open-source-license-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/open-source-license-review"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/open-source-license-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.00033 | $0.02735 |
| Opus 5 | $0.00016 | $0.01367 |
| Sonnet 5 | $0.00007 | $0.00547 |
| Haiku 4.5 | $0.00003 | $0.00274 |
Grade A, and why
Open Source License 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 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open Source License Review
Purpose
Produce a structured, attorney-ready review of the open-source licenses present in a software project or proposed for adoption. The review classifies each license by type, identifies the obligations triggered by the project's distribution model, flags copyleft and license-compatibility conflicts, and surfaces components requiring attorney review. This is draft legal work product — not legal advice and not a legal opinion on compliance.
Use When
- A user asks to "check our open-source dependencies" or "tell me what our OSS obligations are."
- A project is preparing for a product launch, M&A due diligence, or investment round and needs a license inventory review.
- A team is evaluating whether to change how software is distributed (e.g., from internal use to SaaS to binary distribution) and wants to understand the license implications.
- A user has an SBOM (Software Bill of Materials), dependency manifest (
package.json,requirements.txt,go.mod,pom.xml,Cargo.toml, etc.) or similar inventory and wants it reviewed for license risk. - A user is selecting an open-source license for a new project and wants to understand compatibility with existing dependencies.
- A user has received an OSS compliance audit finding or a license violation notice.
Required Inputs
- Component inventory: a list of open-source components and their associated licenses — from an SBOM, dependency manifest, or manual inventory. Each entry should include: component name, version (if available), and license identifier (SPDX identifier preferred, e.g.,
MIT,Apache-2.0,GPL-3.0-only). - Distribution model: how the software is or will be delivered. Examples: internal use only (never distributed outside the organization), distributed binary or package (to end users or customers), SaaS / network service (users access the software over a network but receive no binary), open-source release (source code is published). More than one may apply.
- Proposed outbound license (if applicable): the license the user intends to apply to their own code.
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 · 157 lines · 33 tokens per session scan A 48e1b4a56577
Open Source License Review is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 2,735 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
licensing-brief-writer
Writes a brief summarising the licensing requirements for using a specific piece of music, archive footage, photograph, or other third-party content in a media project — including what licences are needed, who to approach, and what terms to request.
copyright-holder-finder
Produces a step-by-step research plan for identifying the copyright holder of a specific piece of content — image, footage, text, music, or other media — tailored to the content type and jurisdiction.
image-rights-checker
Reviews the details of a specific image and flags potential rights clearance issues before publication, identifying which permissions you likely need and which questions to bring to your legal or picture desk.
creative-commons-explainer
Explains a specific Creative Commons licence in plain language, telling a media professional exactly what they can and cannot do with the licensed content — including attribution requirements, commercial use rules, and derivative work restrictions.
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.