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 skills add aeonfun/aeon --skill compute-resellgit clone --depth 1 https://github.com/aeonfun/aeonWrote 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/aeonfun/aeon/compute-resell)<a href="https://agentmods.dev/skills/aeonfun/aeon/compute-resell"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/compute-resell/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/skills/aeonfun/aeon/compute-resell"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/compute-resell.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.00083 | $0.27966 |
| Opus 5 | $0.00042 | $0.13983 |
| Sonnet 5 | $0.00017 | $0.05593 |
| Haiku 4.5 | $0.00008 | $0.02797 |
Grade B, and why
compute-resell scanned grade B with 2 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 today.
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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
The body above is the shared engine. This section holds the per-provider wiring the *Providers* table points to - read the row for each provider you run. All three create offers with the **same** call: `POST https://api. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Unauthenticated reads (plain `curl`/WebFetch - **no** `secretcurl`, no key). Order-book prices are in **microdollars per 1M tokens** (÷ 1e6 = $/1M): How it starts
The opening of the file, as written. The whole thing — 585 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} -
[<provider>:]<mode>. The optional<provider>prefix (bankr|aws|vertex) restricts the run to one provider; omit it to run every enabled provider (see Providers).<mode>selects the run mode - first match wins:
- empty → the reactive run (the scheduled default): validate the wallet, read the live market + your cost + your usage, auto-list any missing models, reprice every offer against the current market, notify on signal. No separate setup step.
monitor→ read-only market + offers + usage digest, no writes.reprice→ same as empty (kept as an explicit alias).pause→ soft-delete every offer (stop serving); state retained.resume→ re-create offers from state at the current reactive price.Examples: empty = all enabled providers, reactive.
aws= only AWS, reactive.vertex:pause= pause only Vertex.monitor= read-only digest across all enabled providers.(There's no
setupmode - the empty run bootstraps itself: if a provider has no offers yet and its credential is set, it lists that provider's models on the first run.) (You rarely needpause/resumeby hand: the reactive run auto-reaps dead and orphaned offers and auto-relists healthy models - so removing a provider's credential secret already delists it cleanly, and adding a funded one back restores the lineup on the next run. Reach forpause/resumeonly for a deliberate manual hold.)
Providers
This skill is a single reselling engine run once per compute provider. All three providers sell on the same Surplus marketplace with the same create shape (POST /v1/seller/offers with {model, api_key, seller_base_url, ...}); they differ only in the compute source behind the offer - its credential, endpoint, cost basis, and per-account denylist. Everything downstream (market read, scoring, pricing, caps, adaptive discount, reaping, modes, notify) is provider-agnostic and identical for all three.
Provider adapter table - the only per-provider inputs:
| dim | bankr |
aws |
vertex |
|---|---|---|---|
| Surplus seller wallet (secret) | SURPLUS_SELLER_KEY |
SURPLUS_SELLER_AWS_KEY |
SURPLUS_SELLER_VERTEX_KEY |
provider credential → api_key (secret) |
BANKR_LLM_KEY (+ _2/_3) |
BEDROCK_API_KEY |
VERTEX_SERVICE_ACCOUNT_JSON (or VERTEX_API_KEY) |
seller_base_url |
https://llm.bankr.bot/v1 |
BEDROCK_BASE_URL (repo var) |
built from VERTEX_PROJECT_ID + VERTEX_LOCATION (repo vars) |
cost basis C (floor mode) |
/v1/prices bankr entry |
config bedrock_prices |
config vertex_prices |
| config secret | COMPUTE_RESELL_CONFIG |
AWS_COMPUTE_RESELL_CONFIG |
VERTEX_COMPUTE_RESELL_CONFIG |
| state file | memory/state/compute-resell.json |
memory/state/aws-compute-resell.json |
memory/state/vertex-compute-resell.json |
| preflight auth | X-API-Key (Bankr gateway) |
Authorization: Bearer (proxy) |
SA→access-token, or AIza key |
A provider is "enabled" for a run iff its Surplus seller wallet secret and its provider credential secret are both set. Skip (don't error on) any provider missing either - a Bankr-only instance just sets SURPLUS_SELLER_KEY + BANKR_LLM_KEY and never touches AWS/Vertex.
The run loop. Resolve the provider set: [<provider>] from ${var} if it carries a prefix, else every enabled provider. Fetch the shared market reads once - GET /api/markets (roster) and GET /v1/prices (Surplus model catalog) are provider-agnostic, so read them a single time and reuse across providers. Then for each provider in the set, export RESELL_PROVIDER=<provider> (the helper scripts key their config secret + state file off it) and run the full engine below against that provider's adapter row - its own wallet, credential, seller_base_url, cost basis, config, and state file. Providers are independent: one provider failing (bad key, exhausted funds) never aborts the others; log its exit reason and continue. Aggregate one notify at the end (per-provider TLDR lines).
What ships with it
6 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.
- today First seen · 585 lines · 83 tokens per session scan B c730c1bf05fe
compute-resell is a skill published in the GitHub repository aeonfun/aeon (721 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 27,966 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-09.
Other skills, from other repositories
CloudCostOptimizer
Complete FinOps and cloud cost intelligence — AWS/GCP/Azure cost optimization, reserved instance strategy, rightsizing, spot instances, cost allocation, and achieving 30-60% cloud savings without sacrificing reliability.
defi-protocol-templates
Implement DeFi protocols with production-ready templates for staking, AMMs, governance, and flash loans. Use when building decentralized finance applications or smart contract protocols.
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
hybrid-cloud-networking
Configure secure, high-performance connectivity between on-premises infrastructure and cloud platforms using VPN and dedicated connections. Use when building hybrid cloud architectures, connecting data centers to cloud, or implementing secure cross-premises networking.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
terraform-module-library
Build reusable Terraform modules for AWS, Azure, GCP, and OCI infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.