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 commands/solanabr/position-manager-skill/clmm-backtestgit clone --depth 1 https://github.com/solanabr/position-manager-skillWrote 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/solanabr/position-manager-skill/clmm-backtest)<a href="https://agentmods.dev/commands/solanabr/position-manager-skill/clmm-backtest"><img src="https://agentmods.dev/badge/commands/solanabr/position-manager-skill/clmm-backtest.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.00956 |
| Opus 5 | $0.00010 | $0.00478 |
| Sonnet 5 | $0.00004 | $0.00191 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
clmm-backtest 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/clmm-backtest
Backtests a concentrated liquidity range against historical price data, computing net P&L vs HODL and break-even fee-APR requirements.
Steps
-
Prepare inputs - you need: token pair, tick range, optional historical fee data. Set environment:
export OWNER_ADDRESS="YourWallet111..." # optional, for real position ticks -
Run the backtest script (
backtestRangeis pure compute; you supply a price/volume series in quote-per-base terms):npx tsx -e " import { backtestRange } from './skill/templates/il-backtest'; // series: { t: unixSeconds, price: quotePerBase, volume: inQuote }[] const series = [ { t: 1_717_200_000, price: 150, volume: 0 }, { t: 1_717_286_400, price: 158, volume: 2_000_000 }, { t: 1_717_372_800, price: 162, volume: 1_800_000 }, ]; const result = backtestRange({ series, pLow: 140, // range lower price (quote per base) pHigh: 170, // range upper price depositValue: 10000, // initial value in quote (token B) units feeBps: 30, // pool fee tier in basis points (0.30%) // Optional: this position's share of active in-range liquidity (0..1, default 1) // activeShare: 0.05, }); console.log(JSON.stringify(result, null, 2)); " -
Interpret the output (
BacktestResult):{ "lpValue": 10180.2, "hodlValue": 10240.0, "feesEarned": 11.4, "ilFraction": -0.0058, "netVsHodl": -59.8, "feeApr": 0.21, "inRangeFraction": 1.0, "breakEvenWidth": 0.184 }ilFraction: LP principal vs HODL as a fraction (negative = underperforms HODL)feesEarned/feeApr: fees in quote units, annualized over the series durationnetVsHodl: lpValue - hodlValue in quote units (fees included)breakEvenWidth: symmetric half-width w (fraction of p0) where net P&L vs HODL crosses zero on this series;NaNif it never breaks even in the search bounds
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 · 92 lines · 21 tokens per session scan A 6574b84f7ead
clmm-backtest is a command published in the GitHub repository solanabr/position-manager-skill (2 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 956 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.