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 TypeFox/agent-skills --skill eclipse-license-checkgit clone --depth 1 https://github.com/TypeFox/agent-skillsWrote 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/typefox/agent-skills/eclipse-license-check)<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/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/typefox/agent-skills/eclipse-license-check"><img src="https://agentmods.dev/badge/skills/typefox/agent-skills/eclipse-license-check.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.00110 | $0.04208 |
| Opus 5.5 | $0.00044 | $0.01683 |
| Sonnet 5.5 | $0.00022 | $0.00842 |
| Haiku 4.5 | $0.00011 | $0.00421 |
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 1mo 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 — 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
- A local clone of
eclipse-dash/dash-licenses— use it when given; otherwise download the released CLI jar perreferences/dash-license-tool.md. - An IPLab access token — a
gitlab.eclipse.orgpersonal access token withapiscope. 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.
- Inspect:
git -C <path> status --porcelainandgit -C <path> rev-parse --abbrev-ref HEAD. - Clean tree on
master: ifshaded/target/org.eclipse.dash.licenses-*.jaralready exists, use it directly. Otherwisegit -C <path> pull --ff-only, thenmvn -f <path> -DskipTests clean install. Theinstallgoal places both the CLI jar and the Maven plugin into~/.m2so later invocations resolve them locally. Drop-DskipTestsonly to validate the tool itself — the suite hits external services and adds minutes. - 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. - Anything else (modified source/build files, untracked code, other branch, detached HEAD): report what was observed and ask how to proceed.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/evals.json 9.7 KB
- evals/files/.gitignore 31 B
- evals/files/fastbelt-go/go.mod 595 B
- evals/files/fastbelt-go/go.sum 2.7 KB
- evals/files/langium-npm/package-lock.json 21 KB
- evals/files/langium-npm/package.json 2.4 KB
- evals/files/sprotty-yarn/package.json 1.2 KB
- evals/files/sprotty-yarn/yarn.lock 8.3 KB
- references/dash-license-tool.md 15 KB
- references/intellectual-property.md 9.4 KB
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.
- 1mo ago First seen · 214 lines · 110 tokens per session scan A 3691ed329247
eclipse-license-check is a skill published in the GitHub repository TypeFox/agent-skills (5 stars, last pushed 2d ago), licensed MIT. It adds 110 tokens to every session and 4,208 once invoked, about $0.0004 per session on Opus 5.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.
Other skills, from other repositories
EU AI Act High-Risk Obligations
PASS/FAIL/N/A checklist for the high-risk AI obligations under Articles 8-15 of the EU AI Act, plus the quality management system, conformity assessment, registration, post-market monitoring, and incident reporting.
EU AI Act General-Purpose AI
Checklist for the general-purpose AI (GPAI) obligations under Articles 51-55 — technical documentation, copyright policy, training-data summary, and systemic-risk obligations (evaluation, adversarial testing, incident reporting, cybersecurity).
EU AI Act Risk Classification
Decision tree for classifying an AI system into the EU AI Act risk tier (unacceptable/high/limited/minimal) and identifying the actor role (provider/deployer/importer/distributor).
EU AI Act Transparency
Checklist for the Article 50 transparency obligations — chatbot AI disclosure, machine-readable marking of synthetic content, emotion-recognition/biometric-categorisation notice, and deepfake/public-interest-text labelling.
Exception Documentation
The template for documenting a deliberate, approved deviation from an infrastructure invariant — rationale, compensating control, approver, and expiry — instead of a silent workaround.
Agent Design Principles
A checklist for designing agent personas, skills, and multi-agent pipelines that stay reliable as they grow — grounded in the 12-factor-agents principles.