Borrowing it
Nothing to install: this file belongs to ThalesGroup/agilab. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ThalesGroup/agilab/main/.claude/skills/agilab-release-verification/SKILL.mdgit clone --depth 1 https://github.com/ThalesGroup/agilabWrote 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/thalesgroup/agilab/agilab-release-verification)<a href="https://agentmods.dev/skills/thalesgroup/agilab/agilab-release-verification"><img src="https://agentmods.dev/badge/skills/thalesgroup/agilab/agilab-release-verification/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/thalesgroup/agilab/agilab-release-verification"><img src="https://agentmods.dev/badge/skills/thalesgroup/agilab/agilab-release-verification.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.00075 | $0.05522 |
| Opus 5 | $0.00037 | $0.02761 |
| Sonnet 5 | $0.00015 | $0.01104 |
| Haiku 4.5 | $0.00007 | $0.00552 |
Grade C, and why
agilab-release-verification scanned grade C with 2 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 9d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /tmp/agilab-build-check Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
import json, urllib.request The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 9d ago First seen · 498 lines · 75 tokens per session scan C 46581b76aa71
agilab-release-verification is a skill published in the GitHub repository ThalesGroup/agilab (21 stars, last pushed yesterday), with no licence file. It adds 75 tokens to every session and 5,522 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
mlops-collaboration
Prepare a project for public collaboration — license, code of conduct, docs, branch rulesets, templates, and git-cliff releases. Use when open-sourcing a repository, onboarding contributors, or cutting a tagged release.
changelog-orchestrator
Orchestrate 6-phase changelog generation workflow with AI synthesis, multi-source data fetching (GitHub/Slack/Git), quality validation, and automated PR creation. Use when automating release notes, weekly changelogs, or documentation updates. Trigger with "generate changelog", "weekly changelog", or "automate release…
nixtla-release-validation
Multi-phase release validation workflow for nixtla. Analyzes git changes, predicts test impact, assesses risk, runs pytest verification, provides go/no-go recommendation. Trigger: "validate release", "run release validation", "check release readiness".
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.
data-version-control
Data version control with DVC covering pipeline tracking, remote storage, experiment comparison, and reproducible ML workflows for research.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.