DEEIX Chat is an AI workspace that provides one interface for conversations, multiple model providers, files, retrieval, tools, billing, identity, and operational management. Individuals, teams, and enterprises can deploy it to work with different AI models through a unified platform, while the catalogue skill adds agent support for the product.
Borrowing it
Nothing to install: this file belongs to DEEIX-AI/DEEIX-Chat. 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/DEEIX-AI/DEEIX-Chat/dev/.codex/skills/release-note-writer/SKILL.mdgit clone --depth 1 https://github.com/DEEIX-AI/DEEIX-ChatWrote 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/deeix-ai/deeix-chat/release-note-writer)<a href="https://agentmods.dev/skills/deeix-ai/deeix-chat/release-note-writer"><img src="https://agentmods.dev/badge/skills/deeix-ai/deeix-chat/release-note-writer.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00900 |
| Opus 5 | $0.00045 | $0.00450 |
| Sonnet 5 | $0.00018 | $0.00180 |
| Haiku 4.5 | $0.00009 | $0.00090 |
Grade A, and why
release-note-writer 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 8d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Note Writer
Overview
Draft release notes from the actual repository diff, not from guesses. Keep the output suitable for a GitHub Release page and focused on what users, admins, operators, or integrators can observe.
Workflow
-
Confirm the comparison target.
- Use the user-provided range exactly when present, for example
v0.1.0...v0.1.1. - Check that refs exist with
git tag --list,git rev-parse, orgit log --oneline --decorate <range>. - Inspect worktree state with
git status --short, but do not include unrelated local dirt in release content unless the user explicitly asks for it.
- Use the user-provided range exactly when present, for example
-
Gather evidence from git.
- Start broad:
git log --oneline --decorate <range>,git diff --name-status <range>, andgit diff --stat <range>. - Read focused diffs for likely product behavior. Prefer files under application, API, route, service, UI, i18n, and shared client layers.
- Use
rgto locate labels, routes, settings, and UI strings that reveal user-facing behavior. - When commit messages and code disagree, trust the code.
- Start broad:
-
Filter the content.
- Include: new capabilities, changed workflows, admin/user controls, integrations, validation behavior, visible errors, security-relevant behavior users must know, performance or reliability improvements that affect use.
- Exclude unless explicitly requested: README/docs-only edits, version bumps, generated docs, CI workflow changes, issue templates, config-example-only edits, tests, refactors with no behavior change, dependency churn, formatting, and internal implementation details.
- Collapse several low-level changes into one release-note item when they support the same user-facing outcome.
-
Classify each item.
Feature: new or newly exposed product capability.Optimization: improved workflow, behavior, compatibility, validation clarity, reliability, or management experience.Fixed: resolved defect, incorrect behavior, missing error handling, broken display, or mismatch.- If an item could fit multiple sections, choose the section most useful to a release reader.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 84 lines · 90 tokens per session scan A da1e1058e898
release-note-writer is a skill published in the GitHub repository DEEIX-AI/DEEIX-Chat (1,437 stars, last pushed 2d ago), licensed Apache-2.0. It adds 90 tokens to every session and 900 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-30.
Other skills, from other repositories
setup-slack-channel
Use for the PROVIDER half of getting a locally running CopilotKit Channels agent to answer in Slack, when no Slack app exists yet — setting up a Channels bot in Slack for the first time, creating the Slack app and its tokens, attaching it to a managed Intelligence Channel, or when a Channel reports setuprequired, sits…
copilotkit-channels
Use for the CODE half of a managed Intelligence Channel with Slack or Microsoft Teams: customising the Channel a CLI-scaffolded project already ships, or — for a project the CLI did not generate — writing the Channel declaration, the long-running host, and the awaited activation call. Teams provider setup is in scope…
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
mem0-integrate
Integrate Mem0 into an existing repository using a goal-driven, TDD pipeline. Detects the repo's language automatically and asks the user to pick between Mem0 Platform (managed) and Mem0 Open Source (self-hosted). Writes failing tests before any implementation. Produces a local feature branch plus .mem0-integration/…
channels-setup
Use when a developer wants to build their first CopilotKit Channels agent and get it answering in Slack or Microsoft Teams — "set up a channel", "connect my agent to Slack", "get my agent into Teams", or starting from nothing and wanting a working channel end to end. Covers the whole path: inspecting or scaffolding…
ima-skill
A unified IMA skill for managing personal notes and knowledge bases through the platform's APIs.