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/iceymoss/go-hichat-api/new-apinpx skills add iceymoss/go-hichat-api --skill new-apigit clone --depth 1 https://github.com/iceymoss/go-hichat-apiWrote 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/iceymoss/go-hichat-api/new-api)<a href="https://agentmods.dev/skills/iceymoss/go-hichat-api/new-api"><img src="https://agentmods.dev/badge/skills/iceymoss/go-hichat-api/new-api.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.1 | $0.00030 | $0.00631 |
| Opus 5 | $0.00015 | $0.00316 |
| Sonnet 5 | $0.00006 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
new-api scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- 手工：`go run apps/<svc>/api/<svc>.go -f apps/<svc>/api/etc/<svc>-sample.yaml`，再 curl What it actually says
在 apps/<svc>/api 里新增一个 HTTP 接口，使用 goctl 重新生成。
步骤
1. 确认输入
- 哪个服务（
apps/下选一个） - 路径与方法（如
POST /v1/im/conversation/mute） - 是否需要 JWT
- 请求 / 响应字段
- 业务逻辑要不要调用某个 RPC（如果要，确认对应
xxxclient已经注入到svc.ServiceContext）
2. 修改 .api
编辑 apps/<svc>/api/<svc>.api：
- 在
type (...)块里加XxxReq/XxxResp—— 可选字段加optional，可选标量在 Go 端用指针 + omitempty - 在对应
@server块下加路由：
@doc "中文描述"
@handler xxxHandler
post /v1/<svc>/path (XxxReq) returns (XxxResp)
3. 重新生成代码
goctl api go -api apps/<svc>/api/<svc>.api -dir apps/<svc>/api -style gozero
goctl 只会生成缺失的 handler/logic 骨架，不会覆盖你已有的实现。生成完检查 internal/handler/routes.go 已加路由。
4. 写 logic
在 apps/<svc>/api/internal/logic/<xxx>logic.go 写业务：
- 调用 RPC：
l.svcCtx.UserRpc.GetUser(l.ctx, &user.GetUserReq{...}) - 错误用
pkg/xerr封装，不要返回原始 error 给客户端 - JSON 序列化用
common.Marshal/Unmarshal（go-backend.md）
5. 测试
- 单元测试：在
internal/logic/<xxx>logic_test.go写 table-driven 测试 - 手工：
go run apps/<svc>/api/<svc>.go -f apps/<svc>/api/etc/<svc>-sample.yaml，再 curl
6. 同步文档
跑 /sync-api-docs 更新 docs/api.md。
严格约束
- 改
.api后必须重跑 goctl，不要手写 handler - 业务只在 logic 层；handler 只做参数绑定 + 调 logic
- 跨服务调用走 RPC，不要直接读对方数据库（
microservice.md） - 可选请求字段：DTO 用指针 + omitempty
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.
- 6d ago First seen · 56 lines · 30 tokens per session scan A 7fa706a84430
new-api is a skill published in the GitHub repository iceymoss/go-hichat-api (41 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 631 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
golang-patterns
Go-specific design patterns and best practices including functional options, small interfaces, dependency injection, concurrency patterns, error handling, and package organization. Use when working with Go code to apply idiomatic Go patterns.
ast-grep
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for…
gen-test
Generate idiomatic tests for Go packages and handlers in the Meshery project.
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-uber-fx
Golang application framework using uber-go/fx — fx.New, fx.Provide, fx.Invoke, fx.Module, fx.Lifecycle hooks, fx.Annotate (name/group/As), fx.Decorate, fx.Supply, fx.Replace, fx.WithLogger, and signal-aware Run(). Apply when using or adopting uber-go/fx, when the codebase imports go.uber.org/fx, or when wiring…