DISPOSABLE / How it works

Share a tool

Share a small tool you actually use, so others can run it or rebuild it with their own agent. There is no sign-up here: tools are added to a public GitHub repository by pull request.

Get the Disposable skill

One skill does both: it shares your tool by pull request after you approve the exact text, and it fetches a tool for you to read before anything runs. It works with agents that support Agent Skills.

Install it with the skills CLI:

npx skills add x-ify/disposable

Or copy the skills/disposable folder from the repository into your agent’s skills folder. View on GitHub ↗

01

Ask your agent

With the Disposable skill installed, your agent writes DISPOSABLE.md with you, shows it to you for approval and opens the pull request.

Share this tool on Disposable.
02

What goes in

A folder tools/<name>/ with DISPOSABLE.md: what it does, an example result, what you need, quick start, a rebuild section and its limits. Small text sources and up to three images can go in the same folder.

Read the DISPOSABLE.md format ↗
03

Checks and review

Automatic checks run on the pull request. The Disposable team reviews it, and merging publishes it. Your GitHub account is shown as the publisher.

View on GitHub ↗

Use or rebuild with your agent

Give your agent the tool’s link. With the skill, it downloads the tool, shows you the full text and any risk signals, and waits for your yes before each step that changes something.

Rebuild this Disposable tool for me: https://disposable.xify.kr/en/tools/…

No GitHub account?

The Disposable skill walks you through it: it opens the sign-up page, tells you which steps only you can do, and continues once you are signed in. It never asks you to paste a password or token. You must be 13 or older to create a GitHub account.

Before you share

  • Choose an open license: CC0-1.0, CC-BY-4.0, MIT or Apache-2.0. Disposable redistributes what is merged.
  • Removing a tool later does not remove it from git history. Never include personal data or secrets.
  • Checks are limited static text checks. Merging is not a safety guarantee.