Borrowing it
Nothing to install: this file belongs to LayZeeDK/angular-typechecker. 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/LayZeeDK/angular-typechecker/main/.claude/skills/atc-use-cve-lite-cli/SKILL.mdgit clone --depth 1 https://github.com/LayZeeDK/angular-typecheckerWrote 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/layzeedk/angular-typechecker/atc-use-cve-lite-cli)<a href="https://agentmods.dev/skills/layzeedk/angular-typechecker/atc-use-cve-lite-cli"><img src="https://agentmods.dev/badge/skills/layzeedk/angular-typechecker/atc-use-cve-lite-cli/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/layzeedk/angular-typechecker/atc-use-cve-lite-cli"><img src="https://agentmods.dev/badge/skills/layzeedk/angular-typechecker/atc-use-cve-lite-cli.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.00170 | $0.01239 |
| Opus 5.5 | $0.00068 | $0.00496 |
| Sonnet 5.5 | $0.00034 | $0.00248 |
| Haiku 4.5 | $0.00017 | $0.00124 |
Grade A, and why
atc-use-cve-lite-cli 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using cve-lite-cli in angular-typechecker
OWASP cve-lite-cli (an OWASP Lab Project) is this repo's
dependency vulnerability scanner. It parses the lockfile, matches packages against the OSV advisory
database, and prints a copy-and-run fix plan. It runs both locally and as a required CI gate, so
a finding it reports is something you have to clear before a PR can merge.
Running the scan
npm run cve-lite # = cve-lite . --fail-on high (the exact command CI runs)
- Scans the root
package-lock.jsonagainst OSV and exits non-zero on any high- or critical-severity advisory (--fail-on highmeans "at or above high"; moderate/low are reported but do not fail). - The
cve-litejob in.github/workflows/ci.ymlruns this same script and sits in the aggregatecijob'sneeds, so a high/critical finding blocks the merge button.mainis PR-only with an empty bypass, so if the gate is stuck (an OSV.dev outage, or a new no-fix advisory), recover via the ruleset-enforcementtoggle documented inAGENTS.md("Lockout recovery"), not by weakening the gate. - Run it before opening a PR that touches
package.json/package-lock.jsonso you catch a finding locally instead of in CI.
Resolving a finding
- Direct dependency ->
cve-lite . --fixapplies validated direct-dependency fixes and rescans, or bump the version yourself. - Transitive dependency -> the fix is an
overridesentry (npm) or apnpm.overridesentry (pnpm). Follow the two rules below -- both were learned the hard way in this repo, and getting them wrong either breaks CI or breaks unrelated consumers.
Rule 1 -- prefer a nested, parent-scoped override; avoid global and version-keyed ones
A global "pkg": "x" override forces every copy of pkg in the tree to x. A version-keyed key
("[email protected]": "...") looks surgical but is not applied consistently across npm 10 and npm 11:
npm 11 rewrites the lockfile while npm 10 does not, so npm ci fails on the Node-22 CI runner with
an EUSAGE "Missing: [email protected] from lock file" error. The portable, targeted form is the
foundational nested one, scoped to just the offending edge:
What ships with it
1 file 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.
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 · 82 lines · 170 tokens per session scan A 4f675453dad0
atc-use-cve-lite-cli is a skill published in the GitHub repository LayZeeDK/angular-typechecker (11 stars, last pushed 2mo ago), licensed MIT. It adds 170 tokens to every session and 1,239 once invoked, about $0.0007 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…