More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Verified Binary Delivery

    1

    Deliver APKs and installers so the receiver installs exactly the build you verified: fingerprint first, verified direct link, byte-count confirmation on their device before install.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Verified Binary Delivery

    Verified Binary Delivery

    Example session with this skill installed

    I rebuilt my game APK after a one-line pricing fix. The new file is exactly the same size as yesterday's build, and my tester installs from her phone browser. How do I make sure she gets this exact build and not yesterday's, and how do we both prove it?

    • Read your context and instructions
    • Compiled the verified binary delivery

    Step 1, freeze and fingerprint. No more rebuilds after this point. The new APK's byte count is identical to yesterday's, which proves nothing either way, so identity comes from the hashes: the MD5 differs from yesterday's build, and the delivery note records the new MD5 as current and yesterday's as superseded, with SHA-256 as the integrity value of record.

    Step 2, platform checks. Zipalign passes. The signing certificate fingerprint matches yesterday's release, so the update will install in place instead of failing as a signature mismatch. Package name and version code are read from the artifact itself, not from the build script.

    Step 3, contents verified against source. The APK is extracted and its bundled web assets compared byte-for-byte with the source tree: all 1,411 asset paths present and identical, so the pricing fix that shipped is the one in the source, not a stale bundle.

    Step 4, channel. The tester downloads through a phone browser, which refuses bare APK downloads, so the APK ships inside a ZIP via a direct storage link. The note records both numbers: the wrapper's byte count (what she sees first) and the APK's own fingerprint (what matters). The link's expiry is written next to it.

    Step 5, receiver confirmation. Before installing, the tester reports the byte count her phone shows for the downloaded file. It matches the fingerprint exactly, so she installs, and the update lands over yesterday's build. The delivery record closes naming the new MD5 as current.

    If the count had mismatched, the instruction would be: do not install, do not troubleshoot that file, re-send through the direct link. A same-size wrong build installs fine and looks fine; only the fingerprint tells it apart.

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

    About this skill

    This skill governs the hand-off of built binaries: APKs, installers, firmware, and archives. Its rule is simple: a build is not delivered when it leaves your machine, it is delivered when the receiver holds bytes identical to the ones you verified. Before anything moves, the artifact is fingerprinted with an exact byte count, MD5, and SHA-256, and those numbers, not a filename or version string, become its identity.

    It then runs platform checks before packaging (zipalign and signing-certificate fingerprint for Android, so updates install in place), verifies the packaged contents against source by extracting the shipped file and comparing every bundled path byte-for-byte, and picks the channel from a decision table: ZIP-wrapped direct link for phone browsers, unwrapped link for desktop, physical transfer when the network cannot be trusted.

    Delivery closes only when the receiver reads back the byte count on their device and it matches the fingerprint before install. Same-size rebuilds, which are common when edits are text-only, are told apart by MD5 in the delivery record, so "the latest" is always a specific, provable file.

    This skill delivers and verifies files; it does not build them, sign them, or install them on the receiver's device. Verification proves the receiver holds identical bytes, not that the build itself is bug-free. If the receiver's device blocks sideloading by policy, delivery is complete once verified bytes are on the device; unblocking the install is a device setting, not a delivery step.

    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 any payment.

    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 24 days ago

    Permissions

    No special permissions declared or detected

    Listed24 days ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    Chat attachment pipelines have demonstrably altered files in transit; in one real case an APK presented as 56.77 MB while the actual file was 37.65 MB. A verified direct link plus a byte-count readback is the reliable path, and the skill treats attachments as unverified until the count matches.

    Matched counts mean the file is right, so look elsewhere: signature mismatch with the previous install, or a nearly full device, which fails installs for reasons unrelated to the artifact. The skill's gotchas cover both before you rebuild anything.

    Each does a different job. The byte count is the check a person can read off a phone screen, MD5 is the fast way to tell same-size builds apart, and SHA-256 is the integrity value of record. Skipping the readback is the step that lets wrong builds through.

    New in Business & Operations