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 agentmods add skills/ebibibi/ebi-agent-chat-relay/releasenpx skills add ebibibi/ebi-agent-chat-relay --skill releasegit clone --depth 1 https://github.com/ebibibi/ebi-agent-chat-relayWrote 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/ebibibi/ebi-agent-chat-relay/release)<a href="https://agentmods.dev/skills/ebibibi/ebi-agent-chat-relay/release"><img src="https://agentmods.dev/badge/skills/ebibibi/ebi-agent-chat-relay/release.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00040 | $0.01073 |
| Opus 5 | $0.00020 | $0.00536 |
| Sonnet 5 | $0.00008 | $0.00215 |
| Haiku 4.5 | $0.00004 | $0.00107 |
Grade A, and why
release 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 5d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ccdb リリース手順
バージョン体系
v1.3.0 ← 手動マイナーリリース(このスキルの対象)
v1.3.1 ← PR マージごとに自動インクリメント(普段は何もしない)
v1.3.2 ← 同上
...
v1.4.0 ← 手動マイナーリリース(このスキルの対象)
- 自動パッチバンプ: 普通の PR をマージするたびに
.1ずつ自動インクリメント。操作不要 - 手動リリース: マイナー/メジャーの区切りを付けたいときに使う(このスキル)
手動リリース手順(「v1.4.0としてリリースして」)
Step 1: リポジトリに入る
cd /home/ebi/claude-code-discord-bridge
git checkout main && git pull
Step 2: ブランチを作る
git checkout -b release/v1.4.0 # バージョンは指定されたものに変える
Step 3: pyproject.toml のバージョンを更新
pyproject.toml の version = "1.3.x" を指定バージョンに書き換える:
version = "1.4.0"
Step 4: CHANGELOG.md を更新
## [Unreleased]セクションを## [1.4.0] - YYYY-MM-DDに変更(今日の日付)- その上に新しい空の
## [Unreleased]セクションを追加
## [Unreleased]
## [1.4.0] - 2026-02-22 ← 今日の日付
### Added
...(既存の Unreleased 内容がここに来る)
Step 5: PR を作成(タイトルに 必ず [release] を含める)
PATH="/home/ebi/.local/bin:$PATH" git add pyproject.toml CHANGELOG.md
PATH="/home/ebi/.local/bin:$PATH" git commit -m "release: v1.4.0 [release]"
git push -u origin release/v1.4.0
gh pr create \
--repo ebibibi/ebi-agent-chat-relay \
--base main \
--title "release: v1.4.0 [release]" \
--body "Release v1.4.0
## Changes
See CHANGELOG.md for details."
⚠️ 重要: PR タイトルに [release] を含めること。これがないと自動パッチバンプが走って v1.4.1 になってしまう。
Step 6: 確認(数分後)
auto-approve により PR が自動マージされ、タグ v1.4.0 と GitHub Release が作成される:
gh release view v1.4.0 --repo ebibibi/ebi-agent-chat-relay
仕組み(裏側)
PR マージ(auto-approve.yml)
└── repository_dispatch: pr-merged
└── auto-version-bump.yml
├── [release] あり → 現在バージョンでタグ & Release(バンプなし)
└── [release] なし → patch++ を main に直接コミット → タグ & Release
- docs-sync PR(翻訳・ドキュメント更新)はバンプも Release も発生しない
- patch-bump は main への直接コミット(
enforce_admins=falseで許可) - リリース時にはえびログ(Discord)に自動通知
よくある失敗
| 状況 | 原因 | 対処 |
|---|---|---|
| v1.4.1 になってしまった | PR タイトルに [release] がなかった |
タグを削除して再度 release PR を作る |
| タグが既に存在するエラー | 同じバージョンでタグを作ろうとした | タグを削除: gh api repos/ebibibi/ebi-agent-chat-relay/git/refs/tags/v1.4.0 --method DELETE |
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.
- 5d ago First seen · 112 lines · 40 tokens per session scan A 8556a5febb13
release is a skill published in the GitHub repository ebibibi/ebi-agent-chat-relay (56 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 1,073 once invoked, about $0.0002 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
switch
How to take part in a Switch room. Load this skill before your first Switch action and whenever Switch comes up — the user mentions Switch, a Switch room or another Switch agent; you are asked to list, join, read or post in a room, create a room or room group, work with references, links or roles, or inspect an agent…
release-manager
Prepare and operate repository releases through a finite, approval-gated hosted workflow. Use when the user asks to inspect release status, check setup, record component impact, create a generated release PR, plan or approve publication, dispatch post-release evidence, or prepare the OpenAI handoff.
senmu-build-delivery
Govern development batches, non-routine Git, repository and release units, artifacts, deployment, rollback, and production state. Not for ordinary implementation.
configure
Set up the Switch connector for Claude Code — register this Claude Code instance as a Switch agent and write the credentials the bundled MCP server and hooks read. Use when the user asks to configure Switch, set up the plugin, register with a Switch server, or when the Switch tools report no identity.
ci-validation-gates
Defensive CI/CD patterns: semver validation, token checks, retry logic, draft detection — earned from v0.8.22.
release-process
Step-by-step release checklist for Squad — prevents v0.8.22-style disasters.