telegram-output-formatting

telegram-output-formatting is a skill for Claude Code, Codex from datacore-one/datacore. It costs 51 tokens per session (1,077 once invoked), scanned A, original, MIT.

A formatting guide for messages sent through Telegram, a chat app. It separates short chat summaries from full reports saved in the project's journal.

In plain words
What is it for?
It helps format task reports, briefings, status lists, and intelligence updates with short titles, bullet points, and clear next steps.
Why use it?
It keeps Telegram updates brief and easy to scan while preserving detailed methods, sources, logs, and reproduction steps in files.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps format task reports, briefings, status lists, and intelligence updates with short titles, bullet points, and clear next steps.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/datacore-one/datacore/telegram-output-formatting
Install

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.

Any agent
npx skills add datacore-one/datacore --skill telegram-output-formatting
Clone the repo
git clone --depth 1 https://github.com/datacore-one/datacore

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for telegram-output-formatting

README.md
[![agentmods](https://agentmods.dev/badge/skills/datacore-one/datacore/telegram-output-formatting/github.svg)](https://agentmods.dev/skills/datacore-one/datacore/telegram-output-formatting)
Your own site
<a href="https://agentmods.dev/skills/datacore-one/datacore/telegram-output-formatting"><img src="https://agentmods.dev/badge/skills/datacore-one/datacore/telegram-output-formatting/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.

agentmods 80×15 button for telegram-output-formatting

Your own site · 80×15
<a href="https://agentmods.dev/skills/datacore-one/datacore/telegram-output-formatting"><img src="https://agentmods.dev/badge/skills/datacore-one/datacore/telegram-output-formatting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,077 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.01077
Opus 5.5 $0.00020 $0.00431
Sonnet 5.5 $0.00010 $0.00215
Haiku 4.5 $0.00005 $0.00108

Measured 20d ago against content hash 2edab49a2cdc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

telegram-output-formatting scanned grade A with 1 finding 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 20d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- `references/openrouter-credit-check.md` — How to check OpenRouter credit balance (python3 urllib workaround for blocklisted curl auth)
.datacore/skills/telegram-output-formatting/SKILL.md · 133 lines

How it starts

The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Telegram Output Formatting

The Rule

Telegram is the memo. The disk is the dossier.

Chat output = short, punchy, scannable. Full reports = committed to the space's journal (<space>/journal/).

Format Rules

Titles

  • Use emojis in section titles: ✅ 🔴 🟢 🟡 📋 🔍 💡 ⚠️
  • Titles are SHORT — 2-4 words max
  • CAPS for status markers when needed (OK, ERROR, DONE)

Lists

  • Use bullet points (•) — NOT hyphens (-)
  • One line per item, no nested sub-bullets deeper than one level
  • Keep items to a single sentence

Length

  • Telegram messages should fit on one phone screen
  • Highlights and takeaways only — "what matters, what's next"
  • If the output would exceed ~15 lines, write a full report to disk and summarize in chat with a pointer to the file

Structure

A typical task report:

emoji TITLE

• Key finding 1
• Key finding 2
• Key finding 3

Next: what to do about it

For multi-item status reports (cron jobs, task lists):

📋 Header

🟢 Item 1 — status
🔴 Item 2 — status
🟢 Item 3 — status

Summary line

What goes to disk, not chat

  • Full methodology and sources
  • Raw data dumps (GitHub API responses, scan logs)
  • Multi-paragraph analysis
  • Reproduction steps for technical issues
  • Anything that would make the message scroll past one screen

Save full reports to: <space>/journal/YYYY-MM-DD-topic.md

Group Chat vs DM

In The Firm group chat: even shorter. Phone screen, quick scan. See the-firm-etiquette for when to respond at all.

In DM with Gregor: the rules above apply.

Why

Gregor reads on a phone. The memo fits on one screen; the dossier lives in the file. Intelligence briefings that dump full analysis into chat are unreadable — the signal drowns in the noise.

Cron Job Deliveries — Executive Summary Format

Cron job responses delivered to Telegram have a stricter format than interactive responses. The user explicitly wants executive summaries, not log dumps.

Rules for cron delivery format:

  • Title: "{Job Title} — {Human-friendly date}" (e.g., "Monday, September 22, 2026") — always include the day of the week, never ISO dates
  • One-line TL;DR: what was done and the headline finding
  • 2-5 bullet points: key findings ranked by importance
  • One-line "What to watch" or "Action this week" closing note
  • Word limits: 150 for daily jobs, 200 for weekly, 300 for monthly
  • If nothing significant happened: respond with exactly [SILENT]

Read the full file on GitHub · 133 lines

Changes

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.

  1. 20d ago First seen · 133 lines · 51 tokens per session scan A 2edab49a2cdc

Subscribe to this mod's changes

telegram-output-formatting is a skill published in the GitHub repository datacore-one/datacore (4 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 1,077 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-27.