admin.hub_clone

A command that copies a dataset from a remote hub into a new local database. It verifies and records the copied data while leaving the current session database unchanged.

In plain words
What is it for?
Use it to create a local database from a hub URL or from a URL found in environment or configuration settings.
Why use it?
It removes the need to manually download, check, rebuild, and record the origin of a dataset.

Command

Install

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.

agentmods
npx agentmods add commands/stratalab/strata-core/admin.hub_clone
Clone the repo
git clone --depth 1 https://github.com/stratalab/strata-core
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 114 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00114
Opus 5 $0.00000 $0.00057
Sonnet 5 $0.00000 $0.00023
Haiku 4.5 $0.00000 $0.00011

Measured yesterday against content hash 3d46056c5afe, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

admin.hub_clone 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 yesterday.

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.

crates/executor/idl/v1/prose/commands/admin.hub_clone.md · 7 lines

What it actually says

Clones a dataset from a hub into a new local database directory. Resolution, download, verification, reconstitution, and origin recording run once behind this command; the session database is not touched. The destination directory must not exist or must be empty. When the hub URL is not given, the layered resolver selects it from the flag, environment, and config layers.

Changes

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.

  1. yesterday First seen · 7 lines · 0 tokens per session scan A 3d46056c5afe

Subscribe to this mod's changes

admin.hub_clone is a command published in the GitHub repository stratalab/strata-core (2 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 114 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-31.