Neva is a statically typed programming language in which programs are message-passing graphs: nodes exchange data through ports and run concurrently by default. It is for developers building compiled programs with dataflow control, visual editing, and interoperability with Go. The catalogue includes skills and instructions for working with Neva.
Borrowing it
Nothing to install: this file belongs to nevalang/neva. 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/nevalang/neva/main/.codex/skills/release-telegram-post/SKILL.mdgit clone --depth 1 https://github.com/nevalang/nevaWrote 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/nevalang/neva/release-telegram-post)<a href="https://agentmods.dev/skills/nevalang/neva/release-telegram-post"><img src="https://agentmods.dev/badge/skills/nevalang/neva/release-telegram-post/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/nevalang/neva/release-telegram-post"><img src="https://agentmods.dev/badge/skills/nevalang/neva/release-telegram-post.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high System Prompt Leakage · line 31 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00029 | $0.00410 |
| Opus 5.5 | $0.00012 | $0.00164 |
| Sonnet 5.5 | $0.00006 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
release-telegram-post 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 2mo 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.
What it actually says
Release Telegram Post
Create a Telegram-ready release announcement in English for the Neva community group.
Workflow
- Read the release context from the prompt: repository, tag, release name, release URL, and release notes.
- Read
.codex/shared/release-marketing.mdfor positioning, CTA, and tone guidance. - Produce a concise Telegram post in English using this high-level structure:
- Line 1:
Neva vX.Y - Release Title - Line 2: standalone release URL
- Short intro paragraph, 1-2 sentences max; state whether there are language-level breaking changes when the notes make that clear
Highlights:label- 6-8 short numbered highlight lines using emoji numerals
- Final CTA paragraph with repo star/share/Open Collective links
- Line 1:
- Keep each highlight line short, concrete, and scannable.
- Make the post ambitious and clear, not dry and not hypey.
- Use Telegram HTML formatting only (
<b>,<i>,<code>,<a href="...">). - Keep the message easy to scan and under 1500 characters.
- Save output to the exact file path requested by the caller.
Output Rules
- Return only the final Telegram message body in the file.
- Do not add wrappers like "Here is your post", "Result:", or "Output:".
- Do not add YAML frontmatter, surrounding quotes, code fences, or unsupported HTML tags.
- Do not reduce the project description to a dry list of technical facts unless they support a stronger product point.
- Do not bury the release URL inside the CTA paragraph; it should appear near the top as a standalone line.
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.
- 2mo ago First seen · 41 lines · 29 tokens per session scan A cdad2a87c98f
release-telegram-post is a skill published in the GitHub repository nevalang/neva (1,086 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 410 once invoked, about $0.0001 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-09-01.
release-telegram-post compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| release-telegram-postnevalang/neva | Skill | 1.1k | 2mo ago | MIT | A | 29 | Codex |
| migrate-oxlintoxc-project/oxc | Skill | 23k | today | MIT | A | 44 | Claude Code, Codex |
| dd-code-generationDataDog/pup | Skill | 1.0k | yesterday | Apache-2.0 | A | 16 | Claude Code |
| mma-investigatorcockroachdb/cockroach | Skill | 33k | 2d ago | none | A | 47 | Claude Code |
| migrate-state-managementSigNoz/signoz | Skill | 33k | yesterday | none | A | 64 | Claude Code |
| Linux Malware Analysisbuzzer-re/Rikugan | Skill | 706 | 2d ago | MIT | B | 43 | Claude Code, Codex |
| lsp-local-symbolsblackwell-systems/agent-lsp | Skill | 172 | yesterday | MIT | A | 54 | Claude Code |