upload mirage plugin version 0.0.1

[ki3nd]

Plugin Submission

Plugin information

• Author: ki3nd
• Plugin name: mirage
• Version: 0.0.1
• Source repository: https://github.com/ki3nd/mirage-plugin
• Contact: trungkienty2001@gmail.com

Submission type

• New plugin
• Version update

What changed

Initial release of mirage — a tool plugin that lets a Dify agent run bash commands across external resources (S3, Slack, Redis, RAM, GitHub, Postgres, Hugging Face, and more) exposed as one unified virtual filesystem via Mirage.

Two tools:

• execute — run a bash command inside a Mirage workspace; returns stdout, stderr, and exit_code. Supports pipes and cross-resource operations (e.g. grep -r alert /slack | wc -l, cp /s3/report.csv /data/).
• snapshot — export the current workspace as a downloadable tar archive (optionally gzip-compressed).

Key behaviors:

• Runs the Mirage engine in a local daemon subprocess (127.0.0.1) and talks to it over HTTP, keeping live connections and a warm read cache between calls.
• Each conversation gets its own isolated workspace (keyed by config + conversation); idle workspaces are evicted automatically.
• Secrets live only in the encrypted provider credentials and are injected locally as ${UPPERCASE} placeholders — never exposed in tool parameters or to the model; redacted from error messages.
• Read-only by default; writes require an explicit mode: WRITE in the workspace YAML.

Required checks

• I have read and followed the Marketplace submission requirements.
• I have read and comply with the Plugin Developer Agreement.
• I tested this plugin on Dify Community Edition and Dify Cloud, or documented any limitation below.
• The package contains only files needed at runtime.
• The package does not contain secrets, local credentials, .env files, .git directories, virtual environments, caches, logs, or IDE files.
• The package does not contain executables or bundled binaries, or I explained why they are required below.
• The plugin README includes setup steps, usage instructions, required APIs or credentials, connection requirements, and the source repository link.
• The plugin includes PRIVACY.md or a hosted privacy policy, and manifest.yaml references it.
• All user-facing text is primarily in English, with any localized README files following the i18n guidance.

Security and privacy notes

Local validation

Reviewer notes