license-engineer

license-engineer is an agent for Claude Code from alexmmatos/essentials-claude-code. It costs 37 tokens per session (1,596 once invoked), scanned A, original, no licence file.

A specialist for software licensing systems, including open-source license choices, dependency compliance, proprietary software deployment, and risk monitoring. OSI is the organization that maintains a widely used definition of open-source licenses.

In plain words
What is it for?
Use it to choose licenses, build dependency compliance processes, plan proprietary deployments, and monitor licensing risks.
Why use it?
It helps reduce legal and operational risks when software includes dependencies with different licenses or is distributed commercially.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

Part of the essentials-claude-code plugin — 3 skills, 3 commands, 156 agents, 1 hook shipped together

Good fit Use it to choose licenses, build dependency compliance processes, plan proprietary deployments, and monitor licensing risks.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/alexmmatos/essentials-claude-code/license-engineer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/alexmmatos/essentials-claude-code

Made for: Claude Code.

Or install essentials-claude-code, the plugin that ships this one along with the rest of its 3 skills, 3 commands, 156 agents, 1 hook.

Wrote 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.

agentmods badge for license-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/alexmmatos/essentials-claude-code/license-engineer.svg)](https://agentmods.dev/agents/alexmmatos/essentials-claude-code/license-engineer)
Your own site
<a href="https://agentmods.dev/agents/alexmmatos/essentials-claude-code/license-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/essentials-claude-code/license-engineer.svg" alt="Measured on agentmods" height="20"></a>
Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,596 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.01596
Opus 5 $0.00018 $0.00798
Sonnet 5 $0.00007 $0.00319
Haiku 4.5 $0.00004 $0.00160

Measured 5d ago against content hash 5afad0cfcfd9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

license-engineer 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 5d 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.

.claude/agents/license-engineer.md · 296 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 5d ago First seen · 296 lines · 37 tokens per session scan A 5afad0cfcfd9

Subscribe to this mod's changes

license-engineer is an agent published in the GitHub repository alexmmatos/essentials-claude-code (1 stars, last pushed 2mo ago), with no licence file. It adds 37 tokens to every session and 1,596 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.

Related

Other agents, from other repositories

legal-policy

Legal, Compliance, and Policy Validator.

PlanVault/ai-engineering-playbook · 10 tokens

product-manager

Converts feature asks into structured specifications with user stories, acceptance criteria, and scope boundaries.

zachjxyz/jvn · 21 tokens

the-program-manager

Use for multi-team, multi-month technical program management — dependency mapping across teams, risk gates per launch phase, adopting orphaned cross-team problems, designing rollout plans with go/no-go criteria, drafting status comms for different audiences, framing escalations. Trigger when the user is running a…

shwetank/bettersense · 155 tokens

the-retro-facilitator

Use when facilitating a team retrospective or post-mortem after a project, incident, or sprint. Trigger for structured retros that produce action items, not just conversation. Distinct from the-incident-responder (real-time incident management) and the-postmortem-facilitator (blameless postmortem after infrastructure…

shwetank/bettersense · 137 tokens

the-status-crafter

Use for recurring operational status reporting — weekly/monthly status updates, stakeholder updates, leadership reports on an ongoing workstream. Trigger phrases include "help me write my weekly status update", "draft a monthly report for leadership", "what should I put in my stakeholder update?", "status email that…

shwetank/bettersense · 172 tokens

project-manager

Project delivery specialist. Invoke for sprint planning, delivery milestones, dependency mapping, RAID logs, status reports, retrospectives, and cross-functional execution coordination. Distinct from product-manager, use this for delivery and execution, not product discovery.

pranav8494/team-of-agents · 50 tokens