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 ivklgn/ai-kit --skill can-i-usegit clone --depth 1 https://github.com/ivklgn/ai-kitWrote 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/ivklgn/ai-kit/can-i-use)<a href="https://agentmods.dev/skills/ivklgn/ai-kit/can-i-use"><img src="https://agentmods.dev/badge/skills/ivklgn/ai-kit/can-i-use.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 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 Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium MCP Rug Pull · line 20 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 28 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00084 | $0.01094 |
| Opus 5 | $0.00042 | $0.00547 |
| Sonnet 5 | $0.00017 | $0.00219 |
| Haiku 4.5 | $0.00008 | $0.00109 |
Grade A, and why
can-i-use 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Can I Use
You are answering whether a web platform feature is safe to use in THIS project — not in the abstract. "Safe" means: supported by the project's declared browser targets, or degradable there without breaking the experience.
Step 1: Resolve the Project's Browser Targets
Find the target matrix, in priority order:
browserslistkey inpackage.json,.browserslistrc, or a shared config referenced from them- Framework defaults when nothing explicit exists (note which framework and version defines them)
tsconfig.jsontarget/libfor JS language-feature floors- No config at all → ask the user what browsers they must support, or state the assumption you're making (e.g. Baseline Widely available) explicitly
When browserslist is configured, resolve it to concrete versions: npx browserslist in the project root. Record the oldest version per browser family — that's what every feature must clear.
Step 2: Establish Support Data for Each Feature
For every feature in question, get real compatibility data — do not answer from memory, support tables change:
- Query caniuse:
https://caniuse.com/?search=<feature>via WebFetch, or the raw data athttps://raw.githubusercontent.com/Fyrd/caniuse/main/features-json/<feature-id>.jsonwhen you know the feature id - For features not in caniuse (many JS APIs, newer CSS), use MDN BCD:
https://developer.mozilla.org/feature pages state browser versions and Baseline status - If
caniuse-liteis already in the project's node_modules,npx browserslist --coveragestyle tooling can cross-check locally - Note the Baseline status when available: Widely available (safe nearly everywhere), Newly available (recent cross-browser — check your matrix's tail), Limited (not cross-browser yet)
Step 3: Compare and Verdict
For each feature, compare its minimum supporting version per browser against the project's oldest target from Step 1:
- SAFE — supported by every resolved target (including partial-support caveats that don't affect the intended use; state them)
- NEEDS FALLBACK — unsupported in some targets but degradable: pair the verdict with the concrete technique
- UNSAFE — required by the use case, unsupported in targets, no viable fallback
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 · 73 lines · 84 tokens per session scan A 95ab62ce3fca
can-i-use is a skill published in the GitHub repository ivklgn/ai-kit (12 stars, last pushed 3d ago), licensed MIT. It adds 84 tokens to every session and 1,094 once invoked, about $0.0004 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
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
flutter-development
Cross-platform development with Flutter and Dart for iOS, Android, Web, Desktop, and embedded. Use when building Flutter apps, implementing Material/Cupertino design, or optimizing Dart code.
electron-desktop
Desktop application development with Electron for Windows, macOS, and Linux. Use when building cross-platform desktop apps, implementing native OS features, or packaging web apps for desktop.
generic-react-ux-designer
Professional UI/UX design expertise for React applications. Covers design thinking, user psychology (Hick's/Fitts's/Jakob's Law), visual hierarchy, interaction patterns, accessibility, performance-driven design, and design critique. Use when designing features, improving UX, solving user problems, or conducting design…
frontend-enhancer
This skill should be used when enhancing the visual design and aesthetics of web applications. It provides modern UI components, design patterns, color palettes, animations, and layout templates. REQUIRES ui-research skill first. Use this skill for tasks like improving styling, creating responsive designs…
generic-design-system
Complete design system reference for any project - colors, typography, spacing, components, animations. Adapts to project theme and tech stack. Use when implementing UI, choosing colors, creating animations, or ensuring brand consistency. For new design systems, use ui-research skill first.