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 borski/travel-hacking-toolkit --skill points-valuationsgit clone --depth 1 https://github.com/borski/travel-hacking-toolkitWrote 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/borski/travel-hacking-toolkit/points-valuations)<a href="https://agentmods.dev/skills/borski/travel-hacking-toolkit/points-valuations"><img src="https://agentmods.dev/badge/skills/borski/travel-hacking-toolkit/points-valuations/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/borski/travel-hacking-toolkit/points-valuations"><img src="https://agentmods.dev/badge/skills/borski/travel-hacking-toolkit/points-valuations.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.00035 | $0.01854 |
| Opus 5.5 | $0.00014 | $0.00742 |
| Sonnet 5.5 | $0.00007 | $0.00371 |
| Haiku 4.5 | $0.00003 | $0.00185 |
Grade A, and why
points-valuations 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Points Valuations
Reference data: data/points-valuations.json
Four sources are aggregated:
- The Points Guy (TPG): optimistic, has affiliate incentive to inflate
- Upgraded Points: moderate
- One Mile at a Time (OMAAT): conservative
- View From The Wing (VFTW): most conservative and theoretically rigorous
Each entry has:
floor— conservative minimum (use this for decision-making)ceiling— optimistic maximumsources— individual values from each publication
Decision Rules
- Default to the floor for "should I burn points on this?" decisions. If a redemption beats the ceiling, it's genuinely exceptional. Say so.
- Below the floor is objectively poor value. Flag it and suggest alternatives.
- TPG systematically overvalues (affiliate incentive). VFTW and OMAAT are more useful for real decisions.
- When floor and ceiling are within 0.1cpp, the value is well-established.
- When floor and ceiling are 0.3cpp+ apart, mention the range and let the user decide.
The Points-vs-Cash Decision Sequence
Run these steps in order for any "should I use points?" question. Each step can end the analysis early; don't skip ahead.
- Compute true cpp with the formula below — total out-of-pocket including award taxes/surcharges, not gross fare. If you don't know the surcharge yet, get it before quoting a cpp; a BA award can swing from 2.5cpp to 0.9cpp on surcharges alone.
- Compare against the program's
floor. Below floor → recommend cash (or a different program), and say why. At/aboveceiling→ call it exceptional explicitly. - Check reachability before valuing further. A great cpp in a program the user can't reach (no balance, no transfer path in
data/transfer-partners.json) is not an option — drop it. - If a transfer is involved, gate through
transfer-bonuses(check expiry against today's date) — an active bonus divides the effective miles cost and can flip step 2's verdict. - Check the opportunity cost of the currency, not just this redemption. UR at 1.3cpp on a flight is a loss if the user's realistic alternative is Hyatt at 1.5-2.0cpp — the benchmark for a transferable currency is its best practical use, not 1.0.
- Compare against the portal quote (actual quote, not assumed rate — Points Boost is dynamic). Transfer wins on miles-count more often than portal wins on simplicity; show both numbers.
- Present cpp math on both sides and a one-line verdict. User preference thresholds (e.g. a personal ~1.5cpp bar) are an overlay the user applies — still surface sub-threshold options when cash is unreasonable or points are expiring, flagged as such.
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 · 112 lines · 35 tokens per session scan A ca07ad21d55c
points-valuations is a skill published in the GitHub repository borski/travel-hacking-toolkit (710 stars, last pushed 6d ago), licensed MIT. It adds 35 tokens to every session and 1,854 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
alpha-vantage
Access real-time and historical stock market data, forex rates, cryptocurrency prices, commodities, economic indicators, and 50+ technical indicators via the Alpha Vantage API. Use when fetching stock prices (OHLCV), company fundamentals (income statement, balance sheet, cash flow), earnings, options data, market…
stock-liquidity
Analyze how liquid a stock is using Yahoo Finance data (yfinance): bid-ask spreads, volume and dollar volume (ADTV), top-of-book and options depth, square-root market impact and slippage estimates, turnover ratio, and Amihud illiquidity, rolled into a liquidity grade. Use this skill whenever the user asks about…
company-valuation
Estimate a public company's intrinsic value with DCF, relative (peer multiple), and sum-of-the-parts (SOTP) methods, then blend them into an implied share price with upside/downside vs the market price, a WACC and terminal-growth sensitivity grid, and bull/base/bear scenarios. Use this skill whenever the user asks…
earnings-recap
Analyze a company's most recent (or a specified past) earnings report from Yahoo Finance data (yfinance): actual vs estimated EPS, surprise size, revenue and margin trends, and the stock's price reaction. Use this skill whenever the user asks how earnings went — beat or miss, earnings surprise, quarterly results, the…
estimate-analysis
Analyze sell-side analyst estimates and how they are changing, using Yahoo Finance data (yfinance): EPS and revenue consensus by period, estimate ranges and dispersion, revision trends over 7/30/60/90 days and up/down revision breadth, growth estimates vs industry, sector, and the S&P 500, and historical estimate…
finance-sentiment
Fetch normalized stock sentiment across Reddit, X.com, financial news, and Polymarket from the Adanos Finance API: buzz score, bullish percentage, mention or trade counts, and trend. Use this skill whenever the user asks how much a stock is being discussed or how hot it is on social platforms, how many Reddit mentions…