Vigia: version-accurate package facts

    1

    Verify real-time npm/PyPI version data, breaking changes, and AI model specs to prevent hallucinated code.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    Vigia: version-accurate package facts

    Example session with this skill installed

    Check if I can use the 'cookies' function from 'next' version 15.0.0 in my server component and if there are any breaking changes from version 14.

    • Read your context and instructions
    • Compiled the vigia

    I have verified the status of the cookies symbol in next@15.0.0 and compared it with the previous major version.

    Package Analysis: next@15.0.0

    MetricDetails
    Packagenext (npm)
    Version15.0.0
    StatusStable
    Verified Date2024-10-21
    Vulnerabilities0 known for this version

    Symbol Change: cookies()

    The cookies() function signature has changed significantly in the transition from version 14 to 15.

    // Next.js 14 Signature (Synchronous)
function cookies(): ReadonlyRequestCookies

// Next.js 15 Signature (Asynchronous)
function cookies(): Promise<ReadonlyRequestCookies>

    Impact Analysis:
    In Next.js 15, cookies() is now asynchronous. Code that previously accessed cookies synchronously will fail or return a Promise instead of the cookie store. You must now await the function call in your Server Components.

    Compatibility Check:

    • Node.js: Requires ^18.17.0
    • React: Requires ^19.0.0-rc

    Next steps

    1. Update your Server Component to be async if it isn't already.
    2. Replace all instances of const cookieStore = cookies() with const cookieStore = await cookies().
    3. Ensure your package.json reflects the React 19 requirement before deploying.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Training data cutoffs lead to hallucinated library versions and deprecated API calls. Code breaks because your agent remembers an older version of an SDK or doesn't know about a recent breaking change.

    What it does

    • Verify package status fetches the latest version, deprecation notices, and required runtimes for npm or PyPI packages.
    • Analyze upgrade impact identifies breaking changes and signature updates when moving between specific versions.
    • Inspect symbol signatures checks if a specific function or import exists in the installed version and retrieves its exact signature.
    • Find compatible versions locates the newest version of a library that works with specific Node.js, React, or Python constraints.
    • Audit vulnerabilities scans exact versions against OSV data to identify security risks and find the nearest fixed version.
    • Compare AI models retrieves live pricing per 1M tokens, context window sizes, and retirement dates for LLMs.

    How to works

    1. Connect the registry by adding the MCP server to your environment or using the stateless REST API.
    2. Query specific versions using tools like symbol_status to verify that the code you are about to write matches the library's actual API.
    3. Review dependency files by passing a package.json or requirements.txt to the check_dependencies tool for a full ecosystem scan.

    Frameworks & tools

    This skill interfaces with npm, PyPI, and OSV (Open Source Vulnerabilities). It integrates with MCP-compatible clients like Claude Code or Cursor and provides a REST API for any HTTP-capable tool.

    Why this beats prompting it yourself

    LLMs rely on training data that is months or years old, making them prone to recommending deprecated APIs. This skill replaces probabilistic memory with deterministic registry data and real-time type definitions.

    Use cases

    • Upgrading a project from Next.js 14 to 15 while identifying async API changes.
    • Resolving "module not found" errors by verifying if a symbol exists in the current version.
    • Picking an LLM based on the most recent pricing and context window limits.
    • Auditing a requirements.txt for known vulnerabilities and finding patch versions.

    Known limitations

    Packages not previously tracked require a short wait for initial analysis. Data from changelogs and descriptions is treated as untrusted text.

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 12 days ago

    • Free to download with an account

    Requires

    Python

    Listed12 days ago

    What's inside

    Frequently Asked Questions