Borrowing it
Nothing to install: this file belongs to vmehera123/leashd. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vmehera123/leashd/main/.claude/skills/telegram-harness/SKILL.mdgit clone --depth 1 https://github.com/vmehera123/leashdWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/vmehera123/leashd/telegram-harness)<a href="https://agentmods.dev/skills/vmehera123/leashd/telegram-harness"><img src="https://agentmods.dev/badge/skills/vmehera123/leashd/telegram-harness/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vmehera123/leashd/telegram-harness"><img src="https://agentmods.dev/badge/skills/vmehera123/leashd/telegram-harness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00090 | $0.02796 |
| Opus 5 | $0.00045 | $0.01398 |
| Sonnet 5 | $0.00018 | $0.00559 |
| Haiku 4.5 | $0.00009 | $0.00280 |
Grade A, and why
telegram-harness 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Telegram + tmux live harness
scripts/_harness/ runs one process that hosts a fake Telegram Bot API (FastAPI) and a real leashd Engine + TmuxAgent + WebConnector + MultiConnector, wired exactly like main._run_multi. You drive it over an HTTP /control/* plane and watch every outbound Bot API call with timestamps — so you can prove streaming, approvals, and plan/auto/task/goal/follow-up behavior against the real pipeline, no real bot needed.
tmux_harness.py— the server (fake Bot API + control plane + real engine).drive.py— the driver/observer CLI.
Throwaway dev tooling (its docstring says "gitignored" but it is committed). It is not part of
pytest/make check.
⚠️ Read before running
- The task store reads your REAL
~/.leashd/sessions.db— the v4 orchestrator's task DB is hardcoded to~/.leashd/and is not isolated bystorage_backend=memory. With the orchestrator on (TASK_ORCH=1, default) it recovers and re-runs your real stale/tasks on startup. Safest: runTASK_ORCH=0. If you must exercise the orchestrator, first confirm there's nothing to recover:
A fakesqlite3 ~/.leashd/sessions.db \ "SELECT count(*) FROM task_runs WHERE phase NOT IN ('completed','failed','escalated','cancelled')" # must print 0 (and check the log shows task recovery count 0 after HARNESS_READY)HOMEdoes not reliably help — claude 2.1.x auth is macOS-keychain-based, so the pane ends up logged out (Please run /login). RealHOMEis still tmux-isolated viatmux_socket_dir. - An untrusted
APPROVED_DIRis now handled, and is worth testing with.await_readydrives claude's folder-trust dialog (both the legacy prompt and the 2.1.2xx "Accessing workspace" one) by selecting the affirmative row. Before that it hung, then Escaped, and the pane exited — so a dir claude has never opened is the reproduction for that class of bug, not something to avoid. Reset one withhasTrustDialogAccepted: falsefor that path in~/.claude.json. drive.pyreadsAPPROVED_DIR/APP_LOG/AUDIT/TG_PORTfrom the env — export the sameAPPROVED_DIRyou launched the harness with (default/tmp/leashd_tmux_harness/repo), or itslog/watchcommands read the wrong files.- Storage is in-memory; runtime is
tmux; you needclaude+tmuxinstalled andclaudeauthenticated (see thetmux-runtimeskill). Restart the harness to pick up code edits (the engine loads modules at startup).
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.
- today Changed · +70 lines adfd0c8861c7
- 9d ago First seen · 84 lines · 90 tokens per session scan A 8daced53aa84
telegram-harness is a skill published in the GitHub repository vmehera123/leashd (5 stars, last pushed today), licensed Apache-2.0. It adds 90 tokens to every session and 2,796 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
asc-shots-pipeline
Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (asc screenshots frame), and screenshot upload (asc screenshots upload). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition…
smoke-test
Run smoke tests against a deployed or local app based on your git diff. Each test uses Skyvern browser tools (navigate, act, validate, screenshot) with Chrome DevTools MCP as fallback. Posts screenshot evidence as PR comments.