Pinned Source Vendoring with Import Closure

    1

    Named files and glob patterns (every `forms/*.pdf`) are added.

    $29

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Pinned Source Vendoring with Import Closure

    Example session with this skill installed

    Vendor the 'auth-engine' repo. Entry point is src/index.mjs. Include all .css files in the styles folder. Use the latest HEAD commit from the local checkout at ../auth-engine.

    • Read your context and instructions
    • Compiled the pinned source vendoring

    I have processed the vendoring request for the auth-engine repository. The import closure was traversed from src/index.mjs, and additional style assets were captured via globbing. Target directory vendor/auth-engine/ has been updated and SOURCE.json generated.

    Vendoring Report

    SourceStatusCommitFilesResult
    auth-engineUpdateda1b2c3d4e5f612Success

    SOURCE.json Preview

    {
      "repository": "https://github.com/org/auth-engine",
      "commit": "a1b2c3d4e5f67890abcdef123456789012345678",
      "why": "Shared authentication logic and UI styles",
      "files": {
        "src/index.mjs": "589dbe77e61864f542511090313c0ad601967d26450689b70b556f8f85f1c422",
        "src/crypto.mjs": "a3f5e1... (truncated)",
        "styles/theme.css": "b2c4d6... (truncated)"
      }
    }
    

    Next steps

    1. Review the changes in vendor/auth-engine/ to ensure all expected dependencies were captured.
    2. Commit both the vendored source files and the SOURCE.json manifest to your repository.
    3. Add node scripts/vendor.mjs --config vendor.config.json --verify to your CI pipeline to prevent local edits.
    SOURCE.json

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

    About this skill

    Reusing a module from another repository you control usually ends in a private package registry (versions, publish step) or in "copy the folder", which picks up uncommitted edits, CRLF conversions and build output and leaves nobody able to say which upstream commit the application ships.

    vendor.mjs reads every file with git show <commit>:<path>, the committed LF blob, never the working copy (a test proves a CRLF working copy with uncommitted lines still vendors the committed bytes). From each entry point it follows relative ES-module imports (static, side-effect and dynamic) transitively, so a module arrives with everything it needs; skipDynamic leaves a chosen optional import behind. Named files and glob patterns (every forms/*.pdf) are added. The target folder is cleared first so removed upstream files do not linger. vendor/<name>/SOURCE.json records repository, commit, reason and a SHA-256 per file.

    --check re-collects at the pinned commit and fails on any difference (rewritten history, edited pins). --verify hashes the vendored files on disk, needs no upstream checkout, and fails on a modified, missing or unpinned file, so a quick fix inside vendor/ fails the build and goes upstream instead. --commit name=sha pins a chosen commit.

    4 tests on real temporary git repositories: import discovery, the full closure with globs and skipDynamic, check vs verify behaviour after a local edit, a stray file, an upstream change and a re-vendor, the blob-vs-working-copy guarantee, and the CLI's exit codes.

    reference/why-git-blobs.md explains the workflow and how to feed the pins into a release receipt or a startup integrity check. Node 18+, git on the PATH, no packages, no network.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Workflow Automation.

    Does not follow bare package specifiers or require() calls. Requires Node 18+ and local git. One commit per source only.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 17 days ago

    Software
    Node.js 18+, gitGit

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Listed17 days ago

    What's inside

    Frequently Asked Questions

    This skill automates the process of pulling source code from other Git repositories while ensuring all sub-dependencies (imports) are captured. It solves the problem of manual code copying and the complexity of managing private npm registries for internal shared libraries.

    It supports any ESM or CJS project running on Node.js 18 or later. While it doesn't resolve bare package specifiers (like standard npm modules), it is optimized for tracking relative file imports within your own source tree.

    The tool generates a SOURCE.json manifest that pins every file to a specific Git commit SHA and SHA-256 hash. You can run the included --verify command in your CI/CD pipeline to automatically fail builds if any vendored code has been tampered with or deleted.

    The purchase includes the core vendoring script (vendor.mjs), a configuration template (vendor.config.json), and comprehensive documentation on how to integrate the integrity checks into your development workflow.

    Unlike a standard copy-paste, this tool uses 'git show' to pull files directly from the repository's database. This ensures you only vendor code that has been officially committed, bypassing uncommitted local changes, build artifacts, or temporary files in the source directory.

    New in Workflow Automation