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 ccashwell/evm-cortex --skill token-bonding-curvesgit clone --depth 1 https://github.com/ccashwell/evm-cortexWrote 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/ccashwell/evm-cortex/token-bonding-curves)<a href="https://agentmods.dev/skills/ccashwell/evm-cortex/token-bonding-curves"><img src="https://agentmods.dev/badge/skills/ccashwell/evm-cortex/token-bonding-curves/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/ccashwell/evm-cortex/token-bonding-curves"><img src="https://agentmods.dev/badge/skills/ccashwell/evm-cortex/token-bonding-curves.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.01616 |
| Opus 5.5 | $0.00017 | $0.00646 |
| Sonnet 5.5 | $0.00008 | $0.00323 |
| Haiku 4.5 | $0.00004 | $0.00162 |
Grade A, and why
token-bonding-curves 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 1mo 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Token Bonding Curves
Concept
A bonding curve is a mathematical function that defines the price of a token as a function of its supply. As supply increases, price increases along the curve. Tokens are minted on buy and burned on sell, with a reserve backing the curve.
price = f(supply)
cost_to_buy(n) = integral(f, supply, supply + n)
proceeds_from_sell(n) = integral(f, supply - n, supply)
Curve Types
| Curve | Formula | Behavior |
|---|---|---|
| Linear | price = m * supply + b |
Steady price increase |
| Polynomial | price = a * supply^n |
Accelerating increase (n>1) |
| Logarithmic | price = a * ln(supply) + b |
Decelerating increase |
| Sigmoid | price = a / (1 + e^(-k*(supply-mid))) |
S-curve with plateau |
| Bancor | price = reserve / (supply * CW) |
Connector weight model |
Linear Bonding Curve Implementation
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;
import {ERC20} from "@openzeppelin/contracts/token/ERC20/ERC20.sol";
import {ReentrancyGuard} from "@openzeppelin/contracts/utils/ReentrancyGuard.sol";
contract LinearBondingCurve is ERC20, ReentrancyGuard {
uint256 public immutable slope; // price increase per token (in wei per token)
uint256 public immutable basePrice; // starting price (in wei per token)
uint256 public reserveBalance;
constructor(uint256 _slope, uint256 _basePrice)
ERC20("BondingToken", "BOND")
{
slope = _slope;
basePrice = _basePrice;
}
/// @notice Price at a given supply level
function priceAtSupply(uint256 supply) public view returns (uint256) {
return basePrice + (slope * supply / 1e18);
}
/// @notice Cost to buy `amount` tokens at current supply
/// @dev Integral of linear function: base*amount + slope*(s1^2 - s0^2) / (2 * 1e18)
function getBuyCost(uint256 amount) public view returns (uint256) {
uint256 s0 = totalSupply();
uint256 s1 = s0 + amount;
uint256 baseCost = basePrice * amount / 1e18;
uint256 slopeCost = slope * (s1 * s1 - s0 * s0) / (2 * 1e36);
return baseCost + slopeCost;
}
/// @notice Proceeds from selling `amount` tokens at current supply
function getSellProceeds(uint256 amount) public view returns (uint256) {
uint256 s0 = totalSupply();
require(amount <= s0, "exceeds supply");
uint256 s1 = s0 - amount;
uint256 baseCost = basePrice * amount / 1e18;
uint256 slopeCost = slope * (s0 * s0 - s1 * s1) / (2 * 1e36);
return baseCost + slopeCost;
}
function buy(uint256 minTokens) external payable nonReentrant {
uint256 cost = getBuyCost(minTokens);
require(msg.value >= cost, "insufficient payment");
reserveBalance += cost;
_mint(msg.sender, minTokens);
uint256 refund = msg.value - cost;
if (refund > 0) {
(bool ok, ) = msg.sender.call{value: refund}("");
require(ok, "refund failed");
}
emit Buy(msg.sender, minTokens, cost);
}
function sell(uint256 amount) external nonReentrant {
require(balanceOf(msg.sender) >= amount, "insufficient balance");
uint256 proceeds = getSellProceeds(amount);
require(proceeds <= reserveBalance, "insufficient reserve");
reserveBalance -= proceeds;
_burn(msg.sender, amount);
(bool ok, ) = msg.sender.call{value: proceeds}("");
require(ok, "transfer failed");
emit Sell(msg.sender, amount, proceeds);
}
event Buy(address indexed buyer, uint256 amount, uint256 cost);
event Sell(address indexed seller, uint256 amount, uint256 proceeds);
receive() external payable {}
}
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.
- 1mo ago First seen · 181 lines · 42 tokens per session scan A c87ac95c3f5b
token-bonding-curves is a skill published in the GitHub repository ccashwell/evm-cortex (131 stars, last pushed 17d ago), licensed MIT. It adds 42 tokens to every session and 1,616 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
mpp-agent
Pay HTTP 402 APIs via Machine Payments Protocol (MPP).
bridge
Cross-chain token transfers using Wormhole and CCTP.
hyperliquid
Hyperliquid L1 perps DEX (69% market share).
marginfi
MarginFi — Solana lending and borrowing.
token-pick
One token recommendation and one prediction market pick - scored, quantified, with a skip branch when signals are weak.
crypto-market-rank
Crypto market rankings and leaderboards. Query trending tokens, top searched tokens, Binance Alpha tokens, tokenized stocks, social hype sentiment ranks, smart money inflow token rankings, top meme token rankings from Pulse launchpad, and top trader PnL leaderboards. Use this skill when users ask about token rankings…