price
Skill7 starsChanged 9 months agoMITView on GitHub
Get real-time token prices from Flare FTSO oracle. Query current prices, historical data, list supported symbols. Triggers on "/price", "ftso price", "token price", "what's the price of".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- menkesu/awesome-pm-skillstheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- menkesu/awesome-pm-skills★ 441same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 68
On-chain only: - no external APIs
- Distinctive: line 89
Use in other scripts:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Price Skill (FTSO)
Unified interface for FTSO price feeds on Flare network.
Quick Command
node skills/ftso/scripts/ftso.js <symbol>Subcommands
| Command | Description |
<symbol> | Get current price for symbol |
<sym1> <sym2>... | Get multiple prices at once |
history <sym> [period] | Historical price data |
list | List all supported symbols |
Usage Examples
# Single price
/price FLR
# Multiple prices
/price FLR XRP ETH BTC
# JSON output
/price FLR --json
# Historical data
/price history FLR 7d
/price history XRP 30d
# List all symbols
/price listSymbol Aliases
These aliases are automatically resolved:
| Alias | Resolves To |
| WFLR | FLR |
| SFLR | FLR |
| FXRP | XRP |
| USD₮0 | USDT |
| USDT0 | USDT |
Supported Symbols
Crypto
- FLR, XRP, ETH, BTC, LTC
- XLM, DOGE, ADA, ALGO
- ARB, AVAX, BNB, FIL
- LINK, MATIC, SOL
- USDC, USDT
Data Source
- On-chain only - no external APIs
- FtsoV2 Contract - official Flare oracle
- ~90 second updates - prices update each voting epoch
Historical Data
The history daemon polls FTSO every 5 minutes and stores locally:
# Start daemon (if not running)
skills/ftso-history/scripts/ensure-daemon.sh
# Query history
/price history FLR 7d
/price history XRP 30dPeriods: 1d, 7d, 14d, 30d, 90d
Integration
Use in other scripts:
const { getPrice, getPrices } = require('skills/ftso/scripts/price.js');
const flrPrice = await getPrice('FLR');
const prices = await getPrices(['FLR', 'XRP', 'ETH']);Contract Reference
| Contract | Address |
| FlareContractRegistry | 0xaD67FE66660Fb8dFE9d6b1b4240d8650e30F6019 |
| FtsoV2 | Resolved dynamically from registry |
Routing Guide
Don't use when...
- Need historical price charts (use
/price historyor external charting) - Want to execute trades (use
/swap) - Checking portfolio value (use
/portfolio)
Use when...
- Getting current token price from FTSO oracle
- Querying multiple prices at once
- Listing supported FTSO feed symbols
Edge Cases
- Symbol aliases auto-resolve: WFLR→FLR, FXRP→XRP, USDT0→USDT
- FTSO updates every ~90 seconds — prices may lag vs CEX
- Some symbols may not have feeds (check
/price list)
Success Criteria
- Returns price with timestamp and voting round
- Multiple symbols return in single response
- JSON mode outputs parseable data
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
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.

