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/foru17/neko-master/releasenpx skills add foru17/neko-master --skill releasegit clone --depth 1 https://github.com/foru17/neko-masterWrote 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/foru17/neko-master/release)<a href="https://agentmods.dev/skills/foru17/neko-master/release"><img src="https://agentmods.dev/badge/skills/foru17/neko-master/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.00047 | $0.00716 |
| Opus 5 | $0.00023 | $0.00358 |
| Sonnet 5 | $0.00009 | $0.00143 |
| Haiku 4.5 | $0.00005 | $0.00072 |
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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Process
Two independent release lines, both driven entirely by git tags:
| Line | Tag | CI workflow | Artifact |
|---|---|---|---|
| Main product | vX.Y.Z |
.github/workflows/docker-build.yml |
Multi-arch Docker image (Docker Hub + GHCR), ~20 min |
| Agent probe | agent-vX.Y.Z |
.github/workflows/agent-release.yml |
Multi-arch agent binaries, ~1 min |
agent-v* does not build Docker images. The agent binary version is injected at build time from the tag via ldflags — there is no version file to bump for the agent.
Main product release
- Version: bump
versionin the rootpackage.jsononly (apps/* keep their own independent versions; the root field is the single source of truth). - Changelog: add a dated section to BOTH
CHANGELOG.md(Chinese) andCHANGELOG.en.md(English), Keep-a-Changelog style (## [X.Y.Z] - YYYY-MM-DD,### 修复/Fixed,### 优化/Changed). Link issue/PR numbers as reference-style links at the section end. Credit external contributors by handle. - Env docs: any new environment variable must be documented in
.env.examplebefore release. - Test gates (all must pass):
pnpm --filter @neko-master/collector exec tsc --noEmit
pnpm --filter @neko-master/collector test
pnpm --filter @neko-master/web exec tsc --noEmit
pnpm --filter @neko-master/web exec next build
- Ship:
git push origin main
git tag -a vX.Y.Z -m "<one-line summary>"
git push origin vX.Y.Z
gh release create vX.Y.Z --title "vX.Y.Z" --notes "<highlights + upgrade notes>"
- Verify CI:
gh run list --limit 3→ the tag-branch "Build and Push Docker Image" run must endcompleted/success. Multi-arch builds can exceed 20 minutes; poll rather than assume.
Agent release
See docs/agent/release.en.md for full details. Short form:
cd apps/agent && go vet ./... && go test ./... && sh -n nekoagent && sh -n install.sh
git tag agent-vX.Y.Z && git push origin agent-vX.Y.Z
Keep AgentProtocolVersion (Go, internal/config/config.go) and the collector's minimum accepted protocol version in sync when the payload changes — the collector rejects too-old agents with HTTP 426.
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 · 58 lines · 47 tokens per session scan A 0af9c609fcb0
release is a skill published in the GitHub repository foru17/neko-master (3,861 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 716 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
data-viz-renderer
Generate self-contained HTML/SVG infographics from JSON data, including stat cards, bar charts, flow diagrams, and mixed dashboards. Offers 8 color palettes and built-in icons with no external dependencies. Triggered when users request data visualization, infographics, charts, or dashboards.
ship
Commit, push, create PR, then after approval check CI and merge. Use when work is done and ready to ship.
grafana-dashboard
Create, view, and manage Grafana dashboards with panels and datasources.
superset-dashboard
Create, view, and manage Superset dashboards with charts and datasets.
os-release
发布 AI Team OS 新版本的完整清单——预检、版本七处锁步、中英双语 CHANGELOG、双份 dist 构建、私有术语扫描、commit/tag、双仓推送、建 GitHub Release 条目并核对 latest 徽章、事后核对。当准备发版、补建漏掉的 Release 条目、或核对已发版本的线上状态时使用。.
chart-designer
Design effective data visualizations and charts. Generate chart configurations for ECharts, Chart.js, and other libraries. Create dashboards and reports.