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/ishida-supsys/oretachi/releasenpx skills add ishida-supsys/oretachi --skill releasegit clone --depth 1 https://github.com/ishida-supsys/oretachiWrote 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/ishida-supsys/oretachi/release)<a href="https://agentmods.dev/skills/ishida-supsys/oretachi/release"><img src="https://agentmods.dev/badge/skills/ishida-supsys/oretachi/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.00000 | $0.01269 |
| Opus 5 | $0.00000 | $0.00634 |
| Sonnet 5 | $0.00000 | $0.00254 |
| Haiku 4.5 | $0.00000 | $0.00127 |
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 4d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Skill
バージョンをバンプし、CHANGELOG.md を更新してコミットする。
使い方
引数なし、または以下を指定:
patch/minor/major— バンプ種別1.2.3のような具体的なバージョン番号
手順
1. 現在バージョンと次バージョンを決定
package.json から現在バージョンを読み取る。
引数で明示的にバージョンが指定された場合はそれを使う。
引数がなければ git log を分析してバンプ種別を提案し、ユーザーに確認を取ってから進む:
BREAKING CHANGEまたはfeat!:/fix!:→ major バンプを提案feat:コミットがあれば → minor バンプを提案fix:/perf:のみ → patch バンプを提案- それ以外 → patch バンプを提案
提案時は以下の形式でユーザーに示す:
コミット分析の結果、minor バンプを提案します。
現在: 0.12.0 → 次バージョン: 0.13.0
よろしいですか？ (別のバージョンを指定することもできます)
ユーザーが承認または別バージョンを指定してから次のステップに進む。
2. git log を取得
git log $(git describe --tags --abbrev=0 2>/dev/null || git rev-list --max-parents=0 HEAD)..HEAD --pretty=format:"%s"
コミットメッセージを以下のセクションに分類:
feat:→ Addedfix:→ Fixedperf:→ Changed (パフォーマンス改善)refactor:→ Changeddocs:→ Documentationci:/chore:/build:/test:→ Other (省略可)BREAKING CHANGE/!:→ 各セクション冒頭に ⚠️ で記載
コミット本文から重要な説明を抽出してリスト項目を簡潔に書く（英語または日本語、既存 CHANGELOG に合わせる）。
3. git remote URL を取得
git remote get-url origin
GitHub URL に変換（例: https://github.com/owner/repo）。SSH形式 ([email protected]:owner/repo.git) も変換する。
4. CHANGELOG.md を更新
taiki-e/parse-changelog が期待する Keep a Changelog 形式で書く。
CHANGELOG.md が存在しない場合は新規作成。存在する場合は ## [Unreleased] セクションの直後に新バージョンセクションを挿入。
フォーマット例:
# Changelog
All notable changes to this project will be documented in this file.
This project adheres to [Semantic Versioning](https://semver.org/).
## [Unreleased]
## [X.Y.Z] - YYYY-MM-DD
### Added
- 新機能の説明
### Fixed
- バグ修正の説明
### Changed
- 変更内容の説明
[Unreleased]: https://github.com/owner/repo/compare/X.Y.Z...HEAD
[X.Y.Z]: https://github.com/owner/repo/compare/OLD.VER...X.Y.Z
重要なルール:
- 末尾にバージョン比較リンクを追加・更新する
Merge branch '...'コミットは無視するchore: releaseやchore: bump versionコミットは無視する- セクションが空の場合はそのセクション見出しを省略する
- 今日の日付を使う
5. バージョン番号を3ファイルで更新
以下の3ファイルのバージョン文字列を新バージョンに書き換える:
package.json—"version": "X.Y.Z"src-tauri/Cargo.toml—version = "X.Y.Z"(package セクション)src-tauri/tauri.conf.json—"version": "X.Y.Z"
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.
- 4d ago First seen · 134 lines · 0 tokens per session scan A 830f4dcf851f
release is a skill published in the GitHub repository ishida-supsys/oretachi (2 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,269 tokens. 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-31.
Other skills, from other repositories
add-new-agent-support
Add a new agent (tool) support to agent-command-sync following the registry pattern.
with-config
A Codex skill with openai.yaml configuration.
standard-skill
A standard test skill for Gemini.
test-skill
A test skill for chimera.
basic-skill
A basic test skill for Claude.
qmd
Search the vault using QMD semantic search. Use PROACTIVELY before reading files. Preference order: (1) MCP tools — mcpqmdquery, mcpqmdget, mcpqmdmultiget, mcpqmdstatus — if they appear in your tool menu, use them first; (2) CLI qmd --index ... as fallback; (3) Grep/Glob only when QMD is not installed. Trigger…