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 skills add agentproto/ts --skill agentpushgit clone --depth 1 https://github.com/agentproto/tsWrote 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/agentproto/ts/agentpush)<a href="https://agentmods.dev/skills/agentproto/ts/agentpush"><img src="https://agentmods.dev/badge/skills/agentproto/ts/agentpush/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/agentproto/ts/agentpush"><img src="https://agentmods.dev/badge/skills/agentproto/ts/agentpush.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 214 Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.Fix: Set explicit rate limits, timeouts, and resource quotas for API calls, file operations, and compute. Implement circuit breakers for runaway loops.
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.00119 | $0.03860 |
| Opus 5.5 | $0.00048 | $0.01544 |
| Sonnet 5.5 | $0.00024 | $0.00772 |
| Haiku 4.5 | $0.00012 | $0.00386 |
Grade A, and why
agentpush 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 29d ago.
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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agentpush — the agentpush ⇄ agentproto transmitter
Bidirectional bridge between an imported agentpush MCP server (Telegram,
etc.) and live agentproto sessions: transmit_message sends outbound and
can bind the recipient to the sending session, and inbound replies from that
contact then route straight into the SAME session as a real user turn —
instead of spawning a brand-new agent for every reply.
Source: packages/runtime/src/transmitter-bindings.ts,
inbound-adapters.ts, outbound-adapters.ts, inbound-router.ts,
inbound-watcher.ts, the inbound_*/transmit_message/telegram_bot_*
tools in orchestration-tools.ts/telegram-bot-creds.ts, and the
POST /inbound(/:slug) routes in http-server.ts. Full reference:
packages/runtime/docs/TRANSMITTER.md.
The model
One TransmitterBindingStore maps
(alias, source, contactRef) -> { sessionId, mode, provider?, lastSeenTs }
alias— the imported MCP alias (agentpush) or bot-token alias (telegram).source— the channel/phone/chat id the message is scoped to.contactRef— the sender's id within that source.sessionId— the agentproto session future inbound replies from this contact should route into.mode—"route"or"route-or-spawn"(the mode this binding was created under).provider— the outbound provider the binding was created through ("agentpush","telegram", …). Defaults to"agentpush".
Bindings live in memory, persist (debounced write) to
~/.agentproto/transmitter-bindings.json, load on construct, and start
empty on a missing/corrupt file rather than throwing. One store instance is
shared across the poll watcher, transmit_message, and the inbound HTTP
routes.
MCP tools that actually exist
All verified against orchestration-tools.ts / telegram-bot-creds.ts —
don't assume a verb exists beyond this list.
| tool | purpose |
|---|---|
transmit_message |
Send outbound through a provider; binds the recipient to a session by default. Registered only when both an MCP proxy and a binding store are wired. |
inbound_watcher_start |
Start a background poller against poll_inbound on an imported agentpush alias; spawns (or routes, per mode) per contact_ref. Returns a watcherId. |
inbound_watcher_stop |
Stop a watcher by id. Cursor position is preserved for a later restart. |
inbound_watcher_list |
List all watchers (running + stopped) with cursor, poll/fire times, spawn count. |
inbound_endpoint_create |
Create/update a provider-agnostic POST /inbound/<slug> webhook endpoint (dialect, alias, mode, optional signing secret). |
inbound_endpoint_list |
List endpoints. Secrets are never emitted. |
inbound_endpoint_delete |
Delete an endpoint by slug. |
telegram_bot_token_set |
Store/rotate a Telegram bot token (0600 file under ~/.agentproto/telegram-bot-creds/), never echoed back. |
telegram_bot_token_status |
Check whether a token is configured (fingerprint/last4 only). |
telegram_bot_set_webhook |
Call Telegram's setWebhook for a bot alias using the stored token. |
mcp_import |
Prerequisite: import the agentpush MCP server under an alias before any tool above can use it. |
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.
- 29d ago Changed · +5 lines 0415f33bd76e
- 1mo ago First seen · 285 lines · 119 tokens per session scan A 56b8c45a8c05
agentpush is a skill published in the GitHub repository agentproto/ts (10 stars, last pushed today), licensed Apache-2.0. It adds 119 tokens to every session and 3,860 once invoked, about $0.0005 per session on Opus 5.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
skill-creator-primer
You MUST load this skill before the skill-creator skill AND before making ANY change to, or conducting a review of ANY Agent Skill. Triggers include creating, editing, reviewing, or contributing to any part of an Agent Skill (description, frontmatter, body, references, scripts, trigger evals, conflicts, etc).
llm-wiki
Use when building or maintaining a self-contained personal knowledge base (an LLM wiki) in plain markdown. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki health, auditing article claims against their sources, critiquing a wiki source's reasoning, superseding stale knowledge, 'add to…
extract-wisdom
Extract wisdom, insights, and actionable takeaways from YouTube videos, blog posts, articles, or text files. Use when asked to extract wisdom or key insights from a given content source.
apply-mantel-styles
Provides guidelines for applying Mantel's brand styles to diagrams and frontend components. Use when asked to create visuals that need to align with Mantel's branding.
home-assistant
This skill should be used when helping with Home Assistant setup, including creating automations, modifying dashboards, checking entity states, debugging automations, and managing the smart home configuration. Use this for queries about HA entities, YAML automation/dashboard generation, or troubleshooting HA issues.
deepeval
Use when discussing or working with DeepEval (the python AI evaluation framework).