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 skills add Zhong-y-j/Hubloom --skill eventsgit clone --depth 1 https://github.com/Zhong-y-j/HubloomWrote 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/zhong-y-j/hubloom/events)<a href="https://agentmods.dev/skills/zhong-y-j/hubloom/events"><img src="https://agentmods.dev/badge/skills/zhong-y-j/hubloom/events/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/zhong-y-j/hubloom/events"><img src="https://agentmods.dev/badge/skills/zhong-y-j/hubloom/events.svg" alt="Reviewed on agentmods" width="80" 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.00075 | $0.00459 |
| Opus 5 | $0.00037 | $0.00230 |
| Sonnet 5 | $0.00015 | $0.00092 |
| Haiku 4.5 | $0.00007 | $0.00046 |
Grade A, and why
events 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 11d 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.
What it actually says
Events（事件处理总则）
本 Skill 是事件玩法总册。支持的事件类型 = 本目录下除 SKILL.md 外、带 frontmatter event: 的 *.md 分册（API 亦据此发现）。
总则（所有事件共用）
- 先按分册规程办事，再交 Respond 总结；禁止未查证就编造业务结论。
- 默认只读：查列表 / 详情、分析、给建议。删除、禁用、改绑、退款执行等写操作，须用户或运维明确确认后才可
call_api。 - 业务接口仍走 MCP（
list_api/call_api）；工具名以list_api返回为准（注意大小写）。 - 对话中若需回顾总则：
read_skill(skill=events)。事件轮次里对应分册通常已注入触发消息，不必再为读分册空转。
分册索引
| 文件 | event | 处理取向 |
|---|---|---|
locker-created.md |
locker.created |
核对登记是否可见、小区绑定是否正确 |
locker-offline.md |
locker.offline |
诊断离线原因与建议，不擅自改设备 |
order-refund.md |
order.refund |
以总结与风险说明为主，默认不执行退款 |
新增事件：在本目录增加 *.md（frontmatter 必填 event），重启服务即可被 POST /v1/events 与 GET /v1/events/types 识别。
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 29 lines · 75 tokens per session scan A 0fc6d036c805
events is a skill published in the GitHub repository Zhong-y-j/Hubloom (14 stars, last pushed 29d ago), licensed Apache-2.0. It adds 75 tokens to every session and 459 once invoked, about $0.0004 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
implementing-api-schema-validation-security
Implement API schema validation using OpenAPI specifications and JSON Schema to enforce input/output contracts and prevent injection, data exposure, and mass assignment attacks.
implementing-api-schema-validation-security
Implement API schema validation using OpenAPI specifications and JSON Schema to enforce input/output contracts and prevent injection, data exposure, and mass assignment attacks.
fastapi
FastAPI best practices and conventions. Use when working with FastAPI APIs, Pydantic models, dependencies, streaming responses including Server-Sent Events (SSE), and serving frontend apps. Keeps FastAPI code clean and up to date with the latest features and patterns.
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally…
printing-press
Set up a new integration, connector, or CLI binding for any API. Wrap or generate a ship-ready Go CLI from an OpenAPI, HAR, or Postman spec via the lean research -> generate -> build -> shipcheck loop. Use when the user says build a CLI, wrap this API, set up a new integration, add a connector, integrate with a…
implementing-api-abuse-detection-with-rate-limiting
Implement API abuse detection using token bucket, sliding window, and adaptive rate limiting algorithms to prevent DDoS, brute force, and credential stuffing attacks.