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-discord-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-discord-post)<a href="https://agentmods.dev/skills/nevalang/neva/release-discord-post"><img src="https://agentmods.dev/badge/skills/nevalang/neva/release-discord-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-discord-post"><img src="https://agentmods.dev/badge/skills/nevalang/neva/release-discord-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 35 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.00462 |
| Opus 5 | $0.00015 | $0.00231 |
| Sonnet 5 | $0.00006 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
release-discord-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 7d 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 Discord Post
Create a Discord-ready release announcement in English for the target Neva Discord news-style channel provided by the caller.
Workflow
- Read the release context from the prompt: repository, target channel name, tag, release name, release URL, and release notes.
- Read
.codex/shared/release-marketing.mdfor positioning, CTA, and tone guidance. - Produce a concise Discord post in English using this high-level structure:
- Line 1: release heading like
Neva vX.Y.ZorNeva vX.Y.Z - Release Title - Optional short punchy framing line when the release has a clear theme
- Short intro paragraph, 1-2 sentences max
HighlightsorWhat shippedlabel- 4-8 short bullet lines with the most relevant release changes
Full notes:label or short CTA line- Final line: release URL by itself
- Line 1: release heading like
- Keep the intro and bullets grounded in the actual release notes. If the notes are sparse, stay conservative and do not invent features or guarantees.
- Optimize for Discord readability: plain text or light Markdown, short paragraphs, scannable bullets, no Telegram-style HTML.
- Keep the tone clear, sharp, mildly energetic, and community-facing. Avoid corporate phrasing and overselling.
- Use
@everyoneonly when the caller explicitly asks for it. - Keep the message under 1800 characters.
- Save output to the exact file path requested by the caller.
Output Rules
- Return only the final Discord message body in the file.
- Do not add wrappers like "Here is your post", "Result:", or "Output:".
- Do not add YAML frontmatter, surrounding quotes, or code fences.
- Do not bury the release URL inside another sentence; keep it on its own final line.
- Prefer short, high-signal bullets over exhaustive coverage of every patch note.
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.
- 7d ago First seen · 44 lines · 29 tokens per session scan A e95c6c9ecf0d
release-discord-post is a skill published in the GitHub repository nevalang/neva (1,079 stars, last pushed 16d ago), licensed MIT. It adds 29 tokens to every session and 462 once invoked, about $0.0001 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-09-01.
Other skills, from other repositories
migrate-oxlint
Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.
performance-lint-rules
Performance review guidance for Oxc linter rule implementations. Use only when reviewing Rust rule code under crates/oxclinter/src/rules/ or when explicitly auditing those rules for performance improvements.
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
redux-to-swr
Migrate React components from Redux + Saga to SWR hooks. Use when converting data fetching from Redux store (reducers, sagas, selectors, connect HOC) to SWR-based hooks in CockroachDB DB Console or cluster-ui.
mma-investigator
Expert system for investigating MMA (Multi-Metric Allocator) behavior on CockroachDB clusters. Helps oncall engineers diagnose load imbalances, understand rebalancing decisions, and identify why MMA did or didn't act.
migrate-state-management
Migrate Redux or React Context to the correct state option (React Query for server state, nuqs for URL/shareable state, Zustand for global client state). Use when refactoring away from Redux/Context, moving state to the right store, or when the user asks to migrate state management.