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/hazelcast/hive/update-hivegit clone --depth 1 https://github.com/hazelcast/hiveWhat 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.01456 |
| Opus 5 | $0.00000 | $0.00728 |
| Sonnet 5 | $0.00000 | $0.00291 |
| Haiku 4.5 | $0.00000 | $0.00146 |
Grade A, and why
update-hive 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hive Library Update — v4
You are helping update the @hazelcast/ui design system from v3 to v4.
Library context
- Package:
@hazelcast/uiat/Users/mykolafant/Desktop/projects/hive - Components:
src/components/— each component has its own.tsx+.module.scss(being replaced with.module.css) - Legacy components:
src/old/— preserved v3 versions, exported via@hazelcast/ui/old - Public API: everything exported from
src/index.ts - Legacy API: everything exported from
src/old/index.ts(subpath@hazelcast/ui/old) - Stories:
__stories__/<Component>.stories.tsx - Tests:
__tests__/<Component>.test.tsx - Styles: global tokens/constants in
styles/
Backward-compat model
v4 is designed for gradual client migration. When a component changes in a breaking way:
- The old version is preserved in
src/components/old/and exported from@hazelcast/ui/old - The new version lives in
src/components/and is exported from@hazelcast/ui(the main entry) - Clients can temporarily import from
@hazelcast/ui/oldto stay unblocked, then migrate at their own pace - Old components are deprecated (not deleted). They will be removed in v5.
This means there are no hard removal deadlines in v4 — only deprecations.
v4 rules
SCSS → CSS
- All
*.module.scssfiles must be migrated to*.module.css - Replace
@use/@forwardwith standard CSS custom properties - Move shared design tokens to CSS variables in
styles/(not SCSS variables/mixins) - Update all
import styles from './Foo.module.scss'→import styles from './Foo.module.css'
Updating an existing component (breaking change)
- Read the current component file (
src/components/<Name>.tsx) and its SCSS module - Copy the current (old) version to
src/components/old/<Name>.tsx— do not modify it - Also copy its SCSS module to
src/components/old/<Name>.module.scss— do not modify it - Add the old component to
src/old/index.ts(create this file if it doesn't exist yet — see structure below) - Now update
src/components/<Name>.tsxwith the new v4 changes - Migrate
src/components/<Name>.module.scss→src/components/<Name>.module.csswith the new styles - Update the story in
__stories__/to reflect the new API - Update the test in
__tests__/— keep tests passing - Log the change in
docs/migration-v4.md
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 · 135 lines · 0 tokens per session scan A 30f1a374bb25
update-hive is a command published in the GitHub repository hazelcast/hive (19 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,456 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
changelog
Generate a new changelog entry by reading all changeset files and creating a properly formatted entry in .changelog/v3.mdx.
extract
Extract the complete design language from a URL — DTCG tokens, Tailwind, Figma vars, motion, voice, components.
zag
Implement a Zag.js component in Ark UI.
check-docs-consistency
Use the check-docs-consistency skill to validate alignment across rootage/design/react docs.
design-tutorial
Interactive guided tour of Naksha — learn commands through real exercises, discover workflows, and get oriented in under 10 minutes.
design-chatbot
Design a complete chatbot or conversational assistant UI — dialog flows, message bubbles, quick replies, typing indicators, error states, and accessibility.