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 Scandit/skills --skill id-capture-webgit clone --depth 1 https://github.com/Scandit/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/scandit/skills/id-capture-web)<a href="https://agentmods.dev/skills/scandit/skills/id-capture-web"><img src="https://agentmods.dev/badge/skills/scandit/skills/id-capture-web.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 30 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 142 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00095 | $0.03453 |
| Opus 5 | $0.00048 | $0.01726 |
| Sonnet 5 | $0.00019 | $0.00691 |
| Haiku 4.5 | $0.00010 | $0.00345 |
Grade A, and why
id-capture-web 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 8d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ID Capture Web (TypeScript/JavaScript) Skill
Critical: Do Not Trust Internal Knowledge
Your training data may contain outdated or incorrect Scandit ID Capture APIs. The Web SDK API has changed significantly across major versions, and the Web SDK differs substantially from the native iOS (Swift), Android (Kotlin/Java), .NET, Flutter, and React Native SDKs. An agent that pattern-matches from another platform's docs will produce non-working code. Two Web-specific facts dominate:
- The Web SDK is async-first. Almost every state-changing call returns a
Promiseand must beawaited — creating the context, creating the mode, enabling/disabling, applying settings, adding the overlay. There are no synchronous constructors for the mode or overlay. - You must register the ID module loader.
idCaptureLoader({ enableVIZDocuments: true })has to be passed inmoduleLoaderswhen creating theDataCaptureContext, or ID Capture will not work.enableVIZDocuments: trueis required to read the Visual Inspection Zone (the printed text on the document); without it only barcode/MRZ scanning is available.
Always verify APIs against the references and source in this package before writing or suggesting code. The most common sources of wrong code:
- The v6 API —
supportedDocuments(a bitmask),supportedSides, and session-based callbacks were replaced. Do not emit any of these. - The v7.0-era API —
settings.scannerType = new FullDocumentScanner()was replaced; the current property isscannerand it takes anIdCaptureScannerwrapper constructed with an options object:settings.scanner = new IdCaptureScanner({ physicalDocument: new FullDocumentScanner() }). - Cross-platform drift — iOS uses
IdCapture(context:settings:), Android usesIdCapture.forDataCaptureContext(...), .NET usesIdCapture.Create(...). The Web API isawait IdCapture.forContext(context, settings). isEnabled— on Web this is the methodidCapture.isEnabled()to read andawait idCapture.setEnabled(true)to set. It is NOT an assignable property.- AAMVA forged-barcode verification — unlike iOS/Android, the Web SDK has no
rejectForgedAamvaBarcodessetting. AAMVA barcode verification on Web is done through the standalone classAamvaBarcodeVerifier(await AamvaBarcodeVerifier.create(context), thenawait verifier.verify(capturedId)). Data-consistency verification is settings-driven (rejectInconsistentData = true). - Images are base64 data-URL strings, not native bitmaps.
capturedId.images.face/.getFrame(IdSide.Front)/.getCroppedDocument(IdSide.Back)returnstring | null(adata:image/...URL), suitable for an<img>src. They are only populated when enabled viasettings.setShouldPassImageTypeToResult(IdImageType.Face, true).
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.
- 8d ago First seen · 164 lines · 95 tokens per session scan A 1963efa1f709
id-capture-web is a skill published in the GitHub repository Scandit/skills (19 stars, last pushed 6d ago), licensed Apache-2.0. It adds 95 tokens to every session and 3,453 once invoked, about $0.0005 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-30.
Other skills, from other repositories
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
next-dev-loop
Verify Next.js runtime behavior after editing app code. Use this skill to confirm a change actually works in a running app — not just that it compiles or type-checks. Combines /next/mcp (Next.js's view) with agent-browser (the browser's view). Requires a running next dev.
playwright-component-testing
Set up component testing with Playwright using a story gallery — scaffold stories and a gallery dev page driven by the built-in mount fixture, no dedicated component-testing runtime. Use when asked to test React or Vue components in isolation with Playwright, or to migrate off @playwright/experimental-ct-react / -vue.
a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.