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/hydra-db/hydradb-claude-code/statusnpx skills add hydra-db/hydradb-claude-code --skill statusgit clone --depth 1 https://github.com/hydra-db/hydradb-claude-codeWrote 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/hydra-db/hydradb-claude-code/status)<a href="https://agentmods.dev/skills/hydra-db/hydradb-claude-code/status"><img src="https://agentmods.dev/badge/skills/hydra-db/hydradb-claude-code/status.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.00037 | $0.00300 |
| Opus 5 | $0.00018 | $0.00150 |
| Sonnet 5 | $0.00007 | $0.00060 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
status 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.
What it actually says
Check HydraDB plugin status for the current workspace:
node "${CLAUDE_PLUGIN_ROOT}/scripts/plugin.mjs" doctor --json
Summarize:
- whether the plugin is configured
- which config layers or files were resolved
- which API base URL is active
- the active sub-tenant
- whether auto-recall and auto-ingest are enabled
- the active
captureMode,searchMode, andingestionMode - the active max prompt context budget
- the active HydraDB read and write timeouts
- how many files and sessions are currently tracked
- any config validation errors
If configuration is missing or broken, point the user to /hydradb:setup. If captureMode is off, mention that manual session saving is available via /hydradb:save-session.
If the user is specifically debugging prompt-time recall, point them to /hydradb:last-recall.
Do not infer that UserPromptSubmit hooks failed or that no HydraDB context was injected based on status output alone. Status only reports configuration and tracked state; use /hydradb:last-recall for prompt-time recall evidence.
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 · 32 lines · 37 tokens per session scan A b43c0e6242b3
status is a skill published in the GitHub repository hydra-db/hydradb-claude-code (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 37 tokens to every session and 300 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-31.
Other skills, from other repositories
manage-mcp-servers
Add, remove, list, or manage MCP servers in the OpenClaw MCP bridge. Use when installing new servers, removing existing ones, listing available/installed servers, checking server status, or troubleshooting MCP connection issues.
korean-autopilot
한국어로 Claude Code 사용법을 묻거나, 한국어로 작업을 지시하는 사용자를 자동으로 감지하고 적절한 Claude Code 커맨드를 실행하거나 안내합니다. Automatically detects Korean-speaking users and helps them navigate Claude Code by executing or suggesting the right commands based on natural language input. Triggers when: user speaks Korean and asks about Claude Code commands…
sync-claude-skills-to-codex
Sync Claude Code skills (plugins + personal) to Codex CLI by copying folders. Creates /bin/list-skills enumerator for skill discovery. Run after installing new Claude plugins.
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
overleaf-sync
Two-way sync between a local paper directory and an Overleaf project, so ARIS audit/edit workflows stay on the local copy while collaborators edit in the Overleaf web UI. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to…