eclipse-license-check

eclipse-license-check is a skill for Claude Code, Codex from TypeFox/agent-skills. It costs 110 tokens per session (4,208 once invoked), scanned A, original, MIT.

A license-checking workflow for reviewing third-party dependencies in Eclipse Foundation projects with the Eclipse Dash License Tool.

In plain words
What is it for?
Use it to check dependency licenses, answer whether a dependency needs review, prepare release due diligence, and optionally file IPLab review requests.
Why use it?
It shows which dependencies may still need attention from the Eclipse intellectual-property team before release.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to check dependency licenses, answer whether a dependency needs review, prepare release due diligence, and optionally file IPLab review requests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/typefox/agent-skills/eclipse-license-check
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.

Any agent
npx skills add TypeFox/agent-skills --skill eclipse-license-check
Clone the repo
git clone --depth 1 https://github.com/TypeFox/agent-skills

Made for: Claude Code, Codex.

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 eclipse-license-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/typefox/agent-skills/eclipse-license-check.svg)](https://agentmods.dev/skills/typefox/agent-skills/eclipse-license-check)
Your own site
<a href="https://agentmods.dev/skills/typefox/agent-skills/eclipse-license-check"><img src="https://agentmods.dev/badge/skills/typefox/agent-skills/eclipse-license-check.svg" alt="Measured on agentmods" height="20"></a>
Per session 110 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,208 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 original 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.00110 $0.04208
Opus 5 $0.00055 $0.02104
Sonnet 5 $0.00022 $0.00842
Haiku 4.5 $0.00011 $0.00421

Measured 7d ago against content hash 3691ed329247, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

eclipse-license-check 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.

skills/eclipse-license-check/SKILL.md · 214 lines

How it starts

The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Eclipse Dependency License Check

Vet the project's third-party dependencies with the Eclipse Dash License Tool. The restricted list in the summary CSV is the deliverable — what still needs IP Team attention before a formal release.

Load references only when a pointer below fires:

  • references/intellectual-property.md — scope questions ("do I need to vet X?", platform boundary, test/build exemptions, manual IPLab issue format).
  • references/dash-license-tool.md — before invoking the tool (install, flags, per-ecosystem recipes, errors, CI).

Optional inputs

  1. A local clone of eclipse-dash/dash-licenses — use it when given; otherwise download the released CLI jar per references/dash-license-tool.md.
  2. An IPLab access token — a gitlab.eclipse.org personal access token with api scope. Needed only to file IPLab review requests automatically. Treat the token as a secret; see "Handling the IPLab token" below.

If neither was mentioned, proceed with the released jar and without filing reviews — do not prompt.

Preflight: preparing a local Dash License Tool clone

If the user provided a clone path, prepare it before any check runs. The user may have work in progress, so do not modify unfamiliar state.

  1. Inspect: git -C <path> status --porcelain and git -C <path> rev-parse --abbrev-ref HEAD.
  2. Clean tree on master: if shaded/target/org.eclipse.dash.licenses-*.jar already exists, use it directly. Otherwise git -C <path> pull --ff-only, then mvn -f <path> -DskipTests clean install. The install goal places both the CLI jar and the Maven plugin into ~/.m2 so later invocations resolve them locally. Drop -DskipTests only to validate the tool itself — the suite hits external services and adds minutes.
  3. Only IDE/OS noise dirty (e.g. .DS_Store, modifications under .settings/ which Eclipse IDE auto-edits on project open, .idea/): none of this is real WIP. Offer to discard those paths and continue as in step 2; don't act unilaterally.
  4. Anything else (modified source/build files, untracked code, other branch, detached HEAD): report what was observed and ask how to proceed.

Read the full file on GitHub · 214 lines

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. 7d ago First seen · 214 lines · 110 tokens per session scan A 3691ed329247

Subscribe to this mod's changes

eclipse-license-check is a skill published in the GitHub repository TypeFox/agent-skills (5 stars, last pushed 5d ago), licensed MIT. It adds 110 tokens to every session and 4,208 once invoked, about $0.0006 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-31.

Related

Other skills, from other repositories

specification-writing

A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.

wanshuiyin/Auto-claude-code-research-in-sleep · 49 tokens

regulatory-research-fallback

Fallback workflow for regulatory research when web extraction tools fail on government PDFs.

HKUDS/OpenSpace · 20 tokens

x-scorecard

OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.

x-cmd/x-cmd · 57 tokens

memstack-business-gdpr

Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…

cwinvestments/memstack · 121 tokens

gesellschaftsrechtliche-satzungen-agb

Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.

Klotzkette/claude-fuer-deutsches-recht · 69 tokens

nda-review

Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…

LegalQuants/lq-ai · 79 tokens