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.
git clone --depth 1 https://github.com/HCAI-Lab-GT/gt-hiveWrote 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/commands/hcai-lab-gt/gt-hive/pace-cost)<a href="https://agentmods.dev/commands/hcai-lab-gt/gt-hive/pace-cost"><img src="https://agentmods.dev/badge/commands/hcai-lab-gt/gt-hive/pace-cost/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/commands/hcai-lab-gt/gt-hive/pace-cost"><img src="https://agentmods.dev/badge/commands/hcai-lab-gt/gt-hive/pace-cost.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.00025 | $0.00821 |
| Opus 5 | $0.00013 | $0.00411 |
| Sonnet 5 | $0.00005 | $0.00164 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
pace-cost 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 10d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cost estimator
Compute the Phoenix charge for a job. The command is a hybrid: it accepts positional arguments for fast use, and falls into a wizard if invoked with no arguments.
Step 1: parse the arguments
$ARGUMENTS is the user's invocation tail. Two cases:
Case A — $ARGUMENTS is non-empty. Parse it as
<gpu-or-cpu> <hours> [qos] [rate]. Examples:
/gt-hive-pace:pace-cost h100 4-> 1× H100, 4 hours, default QOS, no rate supplied (returns billed usage hours only)./gt-hive-pace:pace-cost cpu 24 embers-> CPU job, 24 hours, freeembersQOS (always $0)./gt-hive-pace:pace-cost h200 0.5 inferno 2.50-> 1× H200, 30 minutes (fractional hours are supported), paid QOS, $2.50/GPU-hour user-supplied rate.
If the args do not parse, ask the user to clarify and skip to Case B.
Case B — $ARGUMENTS is empty. Use AskUserQuestion to collect four
inputs: resource (GPU type or CPU), hours (fractional allowed), QOS
(inferno paid / embers free / unsure), and optional per-hour rate.
Step 2: redirect ICE callers
If the user mentions ICE, the answer is one line: ICE jobs are free — there is no charge model and no estimator. Stop.
Step 3: load pace-phoenix and read the cost model
Load the pace-phoenix skill. Read
pace-phoenix/references/cost-model.md for the cost formula
(usage-hours = (resource count) * (walltime hours),
estimated cost = usage-hours * user-supplied rate), the inferno paid
vs embers free rules, and the --rate-cpu-hour / --rate-gpu-hour
inputs the model expects.
The cost model intentionally externalizes hourly rates because PACE
pricing changes; do not hard-code a rate. The user must supply one (in
$ARGUMENTS or via the wizard) or this command falls back to
usage-hours only.
Step 4: compute and report
Compute usage hours from the cost-model formula. Two cases for the report:
With a user-supplied rate: estimate = usage-hours * rate. Report:
Estimate: $X.XX for h on (QOS: , rate $/h).
:
embersis free;infernois paid against yourgts-*charge account.Rates change. If accuracy matters, re-check
cost-model.mdandpace-quotaon the cluster.
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.
- 10d ago First seen · 78 lines · 25 tokens per session scan A 2b27abd9e6f2
pace-cost is a command published in the GitHub repository HCAI-Lab-GT/gt-hive (4 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 821 once invoked, about $0.0001 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 commands, from other repositories
verify-math
Verify a self-authored mathematical result end to end by routing claims across adversarial review, numerical falsification, symbolic or CAS checks, and Lean, then aggregating one report. Use when a theorem, proposition, conjecture, or paper-wide mathematical argument needs the appropriate combination of verification…
replication-package
Scaffold or audit a social-science replication package at a target directory, and audit the manuscript and its archived research objects against FAIR principles.
diff
Quantitative volume comparison between a CadQuery model and a reference STEP file.
simulation-calibrator
Test and refine simulation accuracy with validation loops, bias detection, and continuous improvement frameworks.
arg-diagram
ARG academic-paper diagram mode — standalone structural & conceptual diagram generation.
graphite-morphology-classify
Classify graphite in a cast-iron micrograph per ASTM A247 / ISO 945-1, quantify nodularity, and read the matrix — the single most diagnostic observation in a cast-iron case.