Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/morphicai/openclaw-morphixai/pipedream-proxynpx skills add Morphicai/openclaw-morphixai --skill pipedream-proxygit clone --depth 1 https://github.com/Morphicai/openclaw-morphixaiWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00036 | $0.00345 |
| Opus 5 | $0.00018 | $0.00172 |
| Sonnet 5 | $0.00007 | $0.00069 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
pipedream-proxy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Pipedream Proxy — 已废弃
此 skill 已废弃。 所有功能已迁移到
office-linkskill（基于 MorphixAI）。
迁移指南
| 原 Pipedream 方案 | 新 MorphixAI 方案 |
|---|---|
PIPEDREAM_TOKEN + PIPEDREAM_PROJECT_ID |
MORPHIXAI_API_KEY |
| Pipedream Connect API Proxy | mx_link: action: proxy |
| Pipedream Connected Accounts | mx_link: action: list_accounts |
| 手动构建 proxy 请求 | 使用 mx_* 专用工具（自动处理 URL/认证/格式） |
为什么迁移
- 统一入口：只需 1 个 API Key，不再需要 Pipedream Token + Project ID
- 专用工具：GitLab/GitHub/Jira 等有
mx_*封装，无需手写 API URL - 自动格式转换：如 Jira Markdown→ADF 转换由工具自动完成
- 简化配置：从 3+ 个环境变量减少到 1 个
参考
- 新方案文档：
skills/office-link/SKILL.md - 工具参考：
skills/TOOLS.md
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 34 lines · 36 tokens per session scan A 5fbd3c226379
pipedream-proxy is a skill published in the GitHub repository Morphicai/openclaw-morphixai (0 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 345 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…