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/runxhq/runx/chargenpx skills add runxhq/runx --skill chargegit clone --depth 1 https://github.com/runxhq/runxWrote 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/runxhq/runx/charge)<a href="https://agentmods.dev/skills/runxhq/runx/charge"><img src="https://agentmods.dev/badge/skills/runxhq/runx/charge.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.00021 | $0.00289 |
| Opus 5 | $0.00010 | $0.00144 |
| Sonnet 5 | $0.00004 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
charge 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 4d 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
Charge
charge is the public seller-side contract for a paid operation. Its OSS graph
is deliberately thin: it submits the exact tool call, hosted pricing policy,
opaque returned credential reference, verification capability reference, and
idempotency seed to the approved Runx Hosted payment operation, then requires a
provider readback before the run can close.
Runx Hosted owns pricing validation, challenge and credential semantics, settlement admission, provider credentials, rail execution, idempotency, recovery, and the private payment ledger. The OSS runtime owns the generic provider-effect gate and receipt envelope. It does not implement a payment rail or infer settlement from caller input.
Operator guide
Use this skill when Runx is the provider of a paid operation. Use spend on the
buyer side and refund for a receipt-linked reversal. A hosted connector and
grants for payment.charge and payment.charge.read are required.
Stop on missing or ambiguous policy, credential reference, capability, counterparty, or idempotency material. Refuse raw card, wallet, provider-key, or bearer material. Never release the paid operation unless hosted execution and readback agree on a terminal successful charge.
What ships with it
2 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.
- 4d ago First seen · 32 lines · 21 tokens per session scan A efb60b85fff5
charge is a skill published in the GitHub repository runxhq/runx (84 stars, last pushed yesterday), licensed Apache-2.0. It adds 21 tokens to every session and 289 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-30.
Other skills, from other repositories
beevibe-team-mesh-negotiation
Multi-round negotiation protocol — covers both initiator and peer roles. Use when about to call negotiate(), when receiving a intent block as a peer, or when receiving an 'escalated' sentinel from a blocked respondnegotiate. Covers proposal crafting, counter-strategy, deadlock detection, when to accept early…
beevibe-use-repo
You are the child agent inside a fresh Docker sandbox. Borrow the given GitHub repo, produce a real artifact for the goal, and export it. Do not review the repo. The proof is that it works.
beevibe-discover-repo
Find the best GitHub repo for a goal, then call userepo to run it in a sandbox. Use whenever the user's goal requires a capability you don't have natively and you haven't been given a specific repo.
opencrow-reversing-toolbox
Use the best available portable Python runtime and installed reverse-engineering tooling for binary analysis, symbolic execution, disassembly, emulation, and binary patching. Prefer a detected ctf environment. Use when an agent needs angr, claripy, capstone, unicorn, ghidra-headless, radare2, objdump, strace, ltrace…
sagemath
Run SageMath through an explicit override, a detected environment named sage, or a PATH-resolved command. Use for CTF and cryptography work involving asymmetric cryptography, finite fields, elliptic curves, lattices, polynomial algebra, modular arithmetic, discrete logs, small-root attacks, or PRNG cryptanalysis.
opencrow-network-toolbox
Use the best available portable Python runtime and installed network tooling for packet- and protocol-level CTF tasks. Prefer a detected ctf environment. Use when an agent needs scapy, tshark, tcpdump, nmap, nc, or socat for packet work, capture analysis, or service triage.