How do I install the Agent Paste skill?

Run npx skillmds@latest add zaks-io/agent-paste in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Agent Paste safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Agent Paste?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Agent Paste free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Agent Paste?

zaks-io (@zaks-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Agent Paste by zaks-io — Agent Skill

Name: Agent Paste
Author: zaks-io

Agent Paste

Publish files, folders, reports, demos, and generated artifacts as websites with agent-paste. Use when an agent needs to hand work to a human through a URL, revise an existing Artifact, or read or edit published content. Prefer the agent-paste CLI when shell access is available and the hosted MCP server otherwise.

zaks-io 9f28062 3.1 KB Updated Sep 17, 2026

File contents

agent-paste

Publish a file or folder as an unguessable, no-login website. Revising an Artifact updates the same stable URL.

Prefer HTML over Markdown for reports

When handing a human a report, plan, review, or summary, write it as HTML rather than Markdown so it reads well when opened. A published page can use real typography, layout, color, tables, inline SVG charts, collapsible sections, and images. Claimed Artifacts can also run inline scripts, the Tailwind browser CDN, and HTTPS libraries; ephemeral Artifacts block scripts and network connections, so keep those static. Lead with the finding, keep the data behind each claim in the page, and open the URL once to check it before handing it over.

Publish

Use agent-paste if installed, otherwise run commands through npx @zaks-io/agent-paste. Use --json for agent-consumed output and inspect --help instead of inventing flags.

agent-paste whoami --json
agent-paste publish <path> --json

whoami exits 0 when signed out, so inspect authenticated. If false and browser authentication is possible, run agent-paste login. Otherwise, or when the user requests accountless publishing:

agent-paste publish <path> --ephemeral --json

Preserve a caller-provided --claim-code <clm_...>. Return the result's url; it is the Artifact and opens without login. For ephemeral results, return claim_url only for the optional keep and ownership step. Ephemeral HTML is static until claimed: scripts, connections, forms, frames, objects, and workers are blocked. Service workers remain blocked after claim. Do not seek a separate share link, viewer URL, or visibility command.

Revise instead of republishing

agent-paste publish <path> --artifact-id <artifact-id> --json
agent-paste pull <artifact-id> <remote-path> --json
agent-paste edit <artifact-id> <remote-path> --edits <edits.json> --json

edit accepts an ordered JSON array of { "old_string", "new_string", "replace_all"? }. If a literal match is absent or ambiguous, re-read and correct it. Never silently replace the whole file. Confirm the returned artifact_id and stable url after every update.

Safety and MCP

Publish only the requested path. Check folders, and the data embedded in a report, for credentials, private source, customer data, and unrelated files even though the CLI excludes common secret paths. Never expose API keys, login state, claim tokens, or credential files. Do not retry an indeterminate publish unless the CLI or read-back proves whether it committed.

Without shell access, connect to https://mcp.agent-paste.sh with OAuth and run whoami first. Use publish_artifact, add_revision, or multi_edit. MCP is text-only; use the CLI for folders, binary files, and accountless publishing. Full docs: https://agent-paste.sh/agents.md.

---name: agent-pastedescription: Publish files, folders, reports, demos, and generated artifacts as websites with agent-paste. Use when an agent needs to hand work to a human through a URL, revise an existing Artifact, or read or edit published content. Prefer the agent-paste CLI when shell access is available and the hosted MCP server otherwise.---# agent-pastePublish a file or folder as an unguessable, no-login website. Revising an Artifact updates thesame stable URL.## Prefer HTML over Markdown for reportsWhen handing a human a report, plan, review, or summary, write it as HTML rather than Markdown soit reads well when opened. A published page can use real typography, layout, color, tables,inline SVG charts, collapsible sections, and images. Claimed Artifacts can also run inlinescripts, the Tailwind browser CDN, and HTTPS libraries; ephemeral Artifacts block scripts andnetwork connections, so keep those static. Lead with the finding, keep the data behind each claimin the page, and open the URL once to check it before handing it over.## PublishUse `agent-paste` if installed, otherwise run commands through `npx @zaks-io/agent-paste`. Use`--json` for agent-consumed output and inspect `--help` instead of inventing flags.```shagent-paste whoami --jsonagent-paste publish <path> --json````whoami` exits 0 when signed out, so inspect `authenticated`. If false and browser authenticationis possible, run `agent-paste login`. Otherwise, or when the user requests accountless publishing:```shagent-paste publish <path> --ephemeral --json```Preserve a caller-provided `--claim-code <clm_...>`. Return the result's `url`; it is the Artifactand opens without login. For ephemeral results, return `claim_url` only for the optional keep andownership step. Ephemeral HTML is static until claimed: scripts, connections, forms, frames,objects, and workers are blocked. Service workers remain blocked after claim. Do not seek aseparate share link, viewer URL, or visibility command.## Revise instead of republishing```shagent-paste publish <path> --artifact-id <artifact-id> --jsonagent-paste pull <artifact-id> <remote-path> --jsonagent-paste edit <artifact-id> <remote-path> --edits <edits.json> --json````edit` accepts an ordered JSON array of `{ "old_string", "new_string", "replace_all"? }`. If aliteral match is absent or ambiguous, re-read and correct it. Never silently replace the wholefile. Confirm the returned `artifact_id` and stable `url` after every update.## Safety and MCPPublish only the requested path. Check folders, and the data embedded in a report, forcredentials, private source, customer data, and unrelated files even though the CLI excludescommon secret paths. Never expose API keys, login state, claim tokens, or credential files. Do not retry an indeterminate publish unless the CLI or read-backproves whether it committed.Without shell access, connect to `https://mcp.agent-paste.sh` with OAuth and run `whoami` first.Use `publish_artifact`, `add_revision`, or `multi_edit`. MCP is text-only; use the CLI for folders,binary files, and accountless publishing. Full docs: <https://agent-paste.sh/agents.md>.

Frequently asked questions