agentleFS
runxhqrunxhq/runx/skills/spend/SKILL.md

spend

Skill97 starsChanged 36 days agoApache-2.0View on GitHub

Execute one governed outbound payment through Runx Hosted with approval and provider readback.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use charge for seller-side paid calls, refund for reversals, and settle-invoice when an invoice first needs hosted validation.

    line 22
  2. Distinctive:

    Stop on malformed or ambiguous signals, missing complete authority, absent rail profile, cap or binding drift, missing approval, …

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Spend

spend is the canonical public buyer-side payment contract. The single default runner submits an exact payment signal, full parent authority, explicit hosted rail, opaque rail profile, optional opaque admission material, realm, and stable idempotency seed to Runx Hosted. It closes only after provider readback matches the mutation result.

Runx Hosted owns quote validation, authority attenuation and reservation, aggregate limits, approval admission, credential custody, rail execution, idempotency, recovery, finality, and the private payment ledger. The OSS runtime owns only generic provider permission enforcement and receipt sealing. There is no local real-payment implementation and no automatic mock fallback.

Operator guide

Use charge for seller-side paid calls, refund for reversals, and settle-invoice when an invoice first needs hosted validation. The selected hosted connector needs payment.spend and payment.spend.read grants.

Stop on malformed or ambiguous signals, missing complete authority, absent rail profile, cap or binding drift, missing approval, unavailable hosted execution, or inconsistent readback. Never put card data, wallet keys, provider keys, tokens, or arbitrary endpoints in skill input.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.