What makes Telegram Footer Patch notable?

2K downloads. Trust evidence available

How should Telegram Footer Patch be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Telegram Footer Patch

Add a Telegram private-chat footer (`🧠 Model + 💭 Think + 📊 Context`) to OpenClaw replies, with dry-run preview, backup, syntax validation, rollback, and r...

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

2.0k

Updated

Oct 9, 2026

Version

1.0.11

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 2K downloads reported by the source. Last updated 10/9/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 9, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 9, 2026
Adoption signal: 2K downloadsadoption · observed Oct 9, 2026
Latest release: 1.0.11release · observed Apr 15, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s178ay2k7851fer4psk2swm5bn83g91r:telegram-footer-patch

Install using `clawhub skill install s178ay2k7851fer4psk2swm5bn83g91r:telegram-footer-patch` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/c-joey/telegram-footer-patch before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-c-joey-telegram-footer-patch/snapshot"

Documentation

CLAWHUB

60,708 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: telegram-footer-patch
description: Add a Telegram private-chat footer (`🧠 Model + 💭 Think + 📊 Context`) to OpenClaw replies, with dry-run preview, backup, syntax validation, rollback, and restart guidance.
license: MIT
spdx: MIT
---

# Telegram Footer Patch

![Footer Preview](./assets/footer-preview.jpg)

给 Telegram 私聊回复追加平台层尾注，不依赖模型记忆。

## Features

- Add a Telegram private-chat footer: `🧠 Model + 💭 Think + 📊 Context`
- Support dry-run, backup, rollback, and reapply after upgrades

## 功能

- 给 Telegram 私聊回复追加 `🧠 Model + 💭 Think + 📊 Context` 尾注
- 支持预览、备份、回滚，以及升级后重打

当前实现：优先命中并修改当前版本实际可能生效的 dist 文件（包含 `agent-runner.runtime-*.js`、`reply-*.js`、`compact-*.js`、`pi-embedded-*.js`、`delivery-*.js` 等），支持按内容 anchor 自动发现、自动备份、重复覆盖更新与回滚。**注意：这表示“尽量兼容不同 bundle 布局”，不等于已经证明跨版本都兼容；最终是否修好，以真实 Telegram 私聊回复是否出现脚注为准。**

## 版本支持 / Validation Boundary

- **已实测通过（live Telegram 私聊验收）**：OpenClaw **2026.3.22**
- **对应实际验证的 bundle 路径（2026.3.22）**：`/usr/lib/node_modules/openclaw/dist/agent-runner.runtime-BWpOtdxK.js`
- **已实测通过（live Telegram 私聊验收）**：OpenClaw **2026.4.5**
- **对应实际验证的 bundle 路径（2026.4.5）**：`/usr/lib/node_modules/openclaw/dist/agent-runner.runtime-UIIO4kss.js`
- **已实测通过（live Telegram 私聊验收）**：OpenClaw **2026.4.12**
- **对应实际验证的 bundle 路径（2026.4.12）**：`/usr/lib/node_modules/openclaw/dist/agent-runner.runtime-D6-wGQkR.js` + `/usr/lib/node_modules/openclaw/dist/delivery-iF4EZ9PY.js`
- **2026.4.12 实战结论**：只 patch runner 不够；真实 Telegram delivery/send path 也可能需要 patch，且必须在**真重启（新 PID）**后再做真实私聊验收
- **已完成的静态验证**：`--dry-run`、`--auto-discover --verify`、smoke test、`node --check`
- **未实测覆盖**：其它 OpenClaw 版本、其它 dist 命名/布局、其它未命中的真实 reply/send path
- **发布口径**：除非做过真实 Telegram 私聊验收，否则只能写“可能兼容/已做兼容处理”，不能写“已支持”

## What to consider before installing / 安装前需要考虑的事项

This skill does what it says (patches OpenClaw dist JS files to append a Telegram footer), but it **writes into your OpenClaw installation directory** and requires **Node.js + Python 3**.

Before installing/running:
1) Inspect the scripts yourself and run `--dry-run` to see which files would be touched.
2) Ensure `node` is installed and you have a plan for filesystem permissions (consider a staging instance/container).
3) Confirm backups are created (`*.bak.telegram-footer.*`) and test the revert script.
4) Only run the patch on systems you control and trust.

这项技能的功能正如其名（修改 OpenClaw 分发目录中的 JS 文件，添加 Telegram 页脚），但它会**写入 OpenClaw 安装目录**，并且需要 **Node.js + Python 3**。

安装/运行前：
1) 请自行检查脚本，并运行 `--dry-run` 先预览将会修改哪些文件。
2) 确保已安装 `node`，并规划好文件系统权限（建议先在测试环境/容器中跑）。
3) 确认已创建备份（查找 `*.bak.telegram-footer.*`）并测试还原脚本。
4) 仅在你控制且信任的系统上运行；不确定就先上 staging。

## 使用

### 1) 预览

```bash
python3 scripts/patch_reply_footer.py --dry-run --list-targets
```

### 2) 应用

```bash
python3 scripts/patch_reply_footer.py --auto-discover
python3 scripts/patch_reply_footer.py --auto-discover --verify
```

### 2.5) 跑 smoke test / verify（推荐）

```bash
bash scripts/smoke_test_footer_patch.sh
# 或指定 dist
bash scripts/smoke_test_footer_patch.sh /usr/lib

README.md

# Telegram Footer Patch

![Footer Preview](./assets/footer-preview.jpg)

Patch OpenClaw's Telegram reply pipeline to append a one-line footer in private chats (`🧠 Model + 💭 Think + 📊 Context`).

## What it does
- Adds a one-line footer for Telegram private-chat replies
- Shows model, think level, and context usage in one line
- Supports dry-run preview
- Creates a backup before any file change
- Supports rollback and verification after restart
- Targets current OpenClaw runner bundles and, when needed, the real Telegram delivery path conservatively
- Final success must be confirmed by a real Telegram private-chat reply

## Recommended flow
1. Dry-run
2. Apply
3. Restart the gateway / service with a **true process restart** (**required** to take effect). Do not rely only on hot refresh / SIGUSR1; confirm a new PID if you can.
4. Send a real Telegram private-chat test message and verify the footer in the actual delivered reply

> Smoke test / marker verification only proves the patch hit candidate bundle files. If the real Telegram reply still has no footer, treat it as not fixed yet.

## Validated version boundary
- **Live-validated:** OpenClaw **2026.3.22**
- **Live-validated bundle path (2026.3.22):** `/usr/lib/node_modules/openclaw/dist/agent-runner.runtime-BWpOtdxK.js`
- **Live-validated:** OpenClaw **2026.4.5**
- **Live-validated bundle path (2026.4.5):** `/usr/lib/node_modules/openclaw/dist/agent-runner.runtime-UIIO4kss.js`
- **Live-validated:** OpenClaw **2026.4.12**
- **Live-validated bundle paths (2026.4.12):** `/usr/lib/node_modules/openclaw/dist/agent-runner.runtime-D6-wGQkR.js` and `/usr/lib/node_modules/openclaw/dist/delivery-iF4EZ9PY.js`
- **2026.4.12 lesson:** runner-only patching was not enough; the real Telegram delivery/send path also needed patching before a true restart + real-chat acceptance succeeded
- **Not live-validated:** other OpenClaw versions/builds
- **Claim boundary:** for untested versions, say “may be compatible” / “compatibility logic added”, not “supported”

## Before you run
- This updates OpenClaw frontend bundle files under `.../openclaw/dist/`.
- Run `python3 scripts/patch_reply_footer.py --dry-run` first.
- Confirm backups exist (`*.bak.telegram-footer.*`) and test rollback (`python3 scripts/revert_reply_footer.py --dry-run`).
- Use only on systems you control.

## Key files
- `SKILL.md` — usage guidance
- `scripts/patch_reply_footer.py` — patch script
- `scripts/revert_reply_footer.py` — rollback script
- `CHANGELOG.md` — release notes
- `LICENSE` — MIT license

_meta.json

{
  "ownerId": "kn7ejvj9b9dtr8kdsyzrx4e3ns813yhw",
  "slug": "telegram-footer-patch",
  "version": "1.0.11",
  "publishedAt": 1776256960931
}

CHANGELOG.md

# Changelog

## 1.0.11
- Live-validate OpenClaw `2026.4.12` with a real Telegram private-chat acceptance after a true process restart.
- Document that runner-only patching is insufficient on `2026.4.12`; the real delivery/send path also has to be patched.
- Update patch/revert tooling to include `delivery-*.js` candidates and verify the live-path patch more conservatively.
- Clarify in docs that hot refresh / SIGUSR1 is not enough evidence by itself; acceptance requires a new PID plus a real Telegram private-chat reply showing the footer.

## 1.0.10
- Add a second live validation boundary: OpenClaw `2026.4.5` is now real-world verified via Telegram private-chat acceptance.
- Document the current live-validated bundle path on `2026.4.5`: `agent-runner.runtime-UIIO4kss.js`.
- Update README/SKILL wording so published support claims distinguish between live-validated versions (`2026.3.22`, `2026.4.5`) and merely compatibility-targeted versions.

## 1.0.9
- Clarify version-support wording: live-validated on OpenClaw `2026.3.22` only; untested versions must not be described as “supported”.
- Document the exact live-validated bundle path: `agent-runner.runtime-BWpOtdxK.js`.
- Tighten acceptance wording so smoke test / static patch verification is no longer treated as final proof; real Telegram private-chat reply validation is required.

## 1.0.8
- Remove stray Python bytecode/cache artifacts from the package again.
- Tighten README/SKILL wording to reduce false-positive suspicious scanning while keeping behavior unchanged.

## 1.0.7
- Fix: footer now appends correctly for Telegram streaming replies that use HTML payloads (not just text payloads).
- Fix: patch reapply uses a function replacement to avoid accidental backslash/escape expansion when updating marker blocks.

## 1.0.6
- Add install/run safety notice to docs.
- Add preflight checks and disable Python bytecode cache writes in scripts.

## 1.0.5
- Remove Python bytecode/cache artifacts from the published package (avoid false-positive malware/suspicious flags).

## 1.0.4
- Compatibility update for latest OpenClaw dist bundles.
- Verified current patch flow against local OpenClaw `2026.3.7`.
- Refreshed skill docs to reflect the current footer format and upgrade-aware reapply workflow.

## 1.0.2
- Updated homepage/skill copy to reflect the current footer format: `🧠 Model + 💭 Think + 📊 Context`.
- Added footer preview image to the top of the README.

## 1.0.1
- Added license and maintenance documentation.
- Clarified apply, rollback, and verification steps.
- Added lightweight README for project hygiene.

## 1.0.0
- Initial release: private-chat footer injection, dry-run check, backup, rollback script.

skill-card.md

## Description:

Add a Telegram private-chat footer (`🧠 Model + 💭 Think + 📊 Context`) to OpenClaw replies, with dry-run preview, backup, syntax validation, rollback, and restart guidance.

This skill is ready for commercial/non-commercial use.

## Publisher:

[c-joey](https://clawhub.ai/user/c-joey)

### License/Terms of Use:

MIT-0

## Use Case:

Developers and OpenClaw operators use this skill to patch installed OpenClaw Telegram reply bundles so private-chat responses include model, thinking level, and context usage footer details. It is intended for controlled OpenClaw environments where the operator can dry-run, back up, apply, restart, and verify the patch through a real Telegram private-chat reply.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The skill persistently modifies installed OpenClaw JavaScript bundle files.

Mitigation: Run the dry-run flow first, inspect the target files, and apply the patch only on systems you control, preferably in a staging instance before production.

Risk: Rollback may be unreliable after repeated patch or upgrade cycles.

Mitigation: Keep an independent clean backup of the OpenClaw dist directory and verify rollback behavior before relying on the included revert script.

Risk: Static marker checks and smoke tests do not prove the live Telegram reply path was patched.

Mitigation: After applying the patch, perform a true gateway restart with a new process and confirm a real Telegram private-chat reply shows the footer.

## Reference(s):


## Skill Output:

**Output Type(s):** [Shell commands, Code, Configuration, Guidance]

**Output Format:** [Markdown guidance with inline shell commands and Python script usage]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Produces patch, verification, rollback, and restart guidance; it does not produce model outputs directly.]

## Skill Version(s):

1.0.11 (source: server release metadata and changelog)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 4h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.