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 commands/iceymoss/go-hichat-api/initgit clone --depth 1 https://github.com/iceymoss/go-hichat-apiWhat 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.01810 |
| Opus 5 | $0.00000 | $0.00905 |
| Sonnet 5 | $0.00000 | $0.00362 |
| Haiku 4.5 | $0.00000 | $0.00181 |
Grade A, and why
init 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 3d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/init — 初始化 go-hichat-api 的 CLAUDE.md
为本项目生成（或更新）根 CLAUDE.md，作为 Claude 在本仓库工作的"第一手"指引。
本命令是项目专用版本，覆盖默认 init skill。
工作流
0. 前置检查
- 如果根目录已有
CLAUDE.md：读取它，不要覆盖，进入"补全模式"——只追加缺失部分，保留已有内容；保存前 diff 给用户确认。 - 如果没有：进入"生成模式"。
1. 探测项目结构（自动执行）
读取以下信号，不要让用户重复回答：
- 根目录
README.md、go.mod、hichat2.sh、docker-compose.yaml apps/*子目录，识别每个服务有哪几层（api/、rpc/、ws/、mq/、cron/、models/）- 找出所有
.api与.proto，提炼出对外接口与 RPC 方法概览 - 扫描
pkg/下的共享包，列出关键工具（如pkg/db、pkg/interceptor、pkg/message） - 探测
web/是否存在 + 框架（package.json里的 next/react/bun） - 读取
.claude/rules/*.md，把规则文件作为权威来源链接进 CLAUDE.md，而不是复制内容
2. 与用户确认（最多 3 个问题）
仅当无法从代码推断时才问，每次只问一个，例如：
- 主开发场景（"我会主要在哪几个服务上工作"）——为了在 CLAUDE.md 里给出更针对性的"日常任务速查"
- 是否需要为每个
apps/<svc>/生成子级 CLAUDE.md - 项目是否有未提交的开发约定（沟通群约定、PR 模板）需要写进去
如果用户全部不确定就跳过，按推断写。
3. 生成根 CLAUDE.md
按以下骨架写入项目根目录。保持简短，每节不超过 30 行；细节用链接指向 .claude/rules/ 或 docs/。
# go-hichat-api
HiChat 2.0 — 基于 go-zero 的微服务 IM + 社交 + 动态空间。前后端分离，前端 `web/`（Next.js + Bun + Semi UI）。
## 架构总览
┌── apps//api (HTTP 入口, .api 描述) │ └── 调用 rpcclient ──┐ ├── apps//rpc (gRPC 服务, .proto 描述) │ └── 通过 etcd 注册/发现 ├── apps/im/ws (WebSocket 长连接, 心跳/ack/在线状态) └── apps/task/{mq,cron} (Kafka 消费 + 定时任务)
数据：MySQL（业务表）/ MongoDB（聊天记录）/ Redis（会话/在线）/ Etcd（服务注册）/ Kafka（消息队列）。
## 服务清单
| 服务 | 层 | 入口 | 用途 |
|------|----|------|------|
| user | api + rpc | apps/user | 注册、登录、用户资料、JWT 签发 |
| social | api + rpc | apps/social | 好友、群、申请、管理员 |
| im | api + rpc + ws | apps/im | 会话、聊天记录、读未读、长连接 |
| trend | api + rpc | apps/trend | 动态、点赞、评论、屏蔽 |
| task | mq + cron | apps/task | 异步消费 + 调度任务 |
入口契约：
- HTTP: `apps/<svc>/api/<svc>.api`
- gRPC: `apps/<svc>/rpc/<svc>.proto`
- 自动汇总文档见 `docs/api.md`（运行 `/sync-api-docs` 更新）。
## 启动 / 测试
- 一键起所有服务：`./hichat2.sh`（前置：MySQL/Redis/Etcd/Mongo/Kafka 已起）
- 单服务：`go run apps/<svc>/<layer>/<svc>.go -f apps/<svc>/<layer>/etc/<svc>-sample.yaml`
- 测试：`go test ./... -count=1`
- 前端：`cd web && bun dev`
## 关键约定（必读）
所有约束以 `.claude/rules/` 为权威。修改前请先读对应文件：
- [Go 后端](.claude/rules/go-backend.md) — JSON、错误处理、并发、资源
- [数据库 / Model](.claude/rules/database-model.md) — schema 变更、三库兼容
- [go-zero / goctl](.claude/rules/go-zero.md) — 代码生成、目录约定
- [跨服务调用](.claude/rules/rpc-client.md) — 必须走 RPC 客户端
- [微服务边界](.claude/rules/microservice.md) — 不读对方数据库
- [WebSocket / IM](.claude/rules/websocket-im.md) — ws 连接、心跳、ack
- [MQ / 定时任务](.claude/rules/mq-task.md) — 幂等、消费失败处理
- [测试](.claude/rules/test-files.md) — table-driven、不 mock 数据库
- [前端](.claude/rules/frontend.md) — bun、Semi UI、i18n
## 常见任务速查
| 想做的事 | 用什么 |
|----------|--------|
| 全新功能从需求开始 | `/spec` |
| 新增一个微服务 | `/new-service` |
| 在已有服务加 HTTP 接口 | `/new-api` |
| 加 RPC 方法 | `/new-rpc` |
| 加数据库表 | `/new-model` |
| 启动 / 重启 / 看日志 | `/run-services` |
| 审查当前 diff（Go） | `/goreview` |
| 跑测试 | `/gotest` |
| 同步 API 文档 | `/sync-api-docs` |
| /clear 后恢复上下文 | `/catchup` |
| 新成员上手 | `/onboard` |
## Subagent
复杂或者需要独立上下文的审查工作走 subagent：
- `architecture-reviewer` — 分层职责、模式一致性
- `security-reviewer` — 注入、鉴权、密钥、SSRF
- `api-contract-reviewer` — `.api` / `.proto` 兼容性 / 命名 / optional 标记
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.
- 3d ago First seen · 129 lines · 0 tokens per session scan A af12d2fa14b8
init is a command published in the GitHub repository iceymoss/go-hichat-api (41 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,810 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.