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 Fusion-Data-Company/bristol-os --skill deal-evolutiongit clone --depth 1 https://github.com/Fusion-Data-Company/bristol-osWrote 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/fusion-data-company/bristol-os/deal-evolution)<a href="https://agentmods.dev/skills/fusion-data-company/bristol-os/deal-evolution"><img src="https://agentmods.dev/badge/skills/fusion-data-company/bristol-os/deal-evolution/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/fusion-data-company/bristol-os/deal-evolution"><img src="https://agentmods.dev/badge/skills/fusion-data-company/bristol-os/deal-evolution.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.00082 | $0.01072 |
| Opus 5 | $0.00041 | $0.00536 |
| Sonnet 5 | $0.00016 | $0.00214 |
| Haiku 4.5 | $0.00008 | $0.00107 |
Grade A, and why
deal-evolution 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 10d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deal Evolution — V1 → V2 → V3 (automatic, one prompt)
The skill is the evolution. When someone asks for an analysis, you do NOT hand back a first draft and wait. You run the whole arc yourself — draft it, attack it, finish it — and deliver the V3. The user prompts once.
The discipline (this is the part that matters)
- Finish each version before you plan the next. Do not pre-plan all three. Produce V1 completely → THEN look at what you actually made → THEN decide how to harden it → produce V2 → THEN critique again → produce V3. Plan the next phase only from the finished prior one. (Don't over-plan up front — build, then critique, then build.)
- Each version must already carry full rigor (see
bristol-os/reference/rigor-standard.md). V1 is not "sloppy" — it's the honest first pass with best-available data. V2 and V3 raise verification and depth, not basic competence. - Keep going until V3 meets the bar. Don't stop at V1 or V2 and ask "want me to keep going?" — you already know they do.
V1 — DRAFT (get a real, defensible answer on the page)
- Build the full structure and a first-pass answer using the best data you can pull now (Quarry parcel, FRED/Census live, web/Tavily/Exa, Bristol portfolio calibration).
- Compute the core metrics. Label every estimate as an estimate.
- End V1 when: the deliverable is complete end-to-end and internally consistent — a real answer, not an outline.
Self-critique gate (run between every version — adversarial, in writing to yourself)
Ask, and act on the answers:
- What's estimated that should be sourced? Replace guesses with real, named, cited comps/figures.
- What's unverified or single-source? Confirm across 2+ primary sources; flag what can't be.
- What local detail could be wrong? Jurisdiction, submarket, corridor, school zone, zoning, who owns what — these readers have 20 years here and will catch any off detail. Verify Franklin/Williamson specifics against primary sources.
- What elite metric is missing? (rigor-standard.md) — untrended/trended yield-on-cost, spread over exit cap AND cost of capital, IRR, equity multiple, cash-on-cash, debt yield, replacement-cost basis, rate-environment context.
- What would a Berkshire-level sponsor poke? Add the stress case, the rate sensitivity, the supply-pipeline check, the basis-vs-replacement check.
- Does it reconcile? Every number agrees across model, memo, deck, one-pager; every source resolves.
- Any error? (e.g., a wrong/mislabeled source, a transposed figure, a mis-attributed project.) Fix it.
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.
- 10d ago First seen · 45 lines · 82 tokens per session scan A 58ad94758b60
deal-evolution is a skill published in the GitHub repository Fusion-Data-Company/bristol-os (1 stars, last pushed 2mo ago), licensed MIT. It adds 82 tokens to every session and 1,072 once invoked, about $0.0004 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 skills, from other repositories
trade-idea-generation
Systematic trade idea generation framework, fundamental quantitative and qualitative screening pipeline, catalyst-driven trade structuring, macro-to-micro idea translation, 20-60 day long-short portfolio management process.
chart-patterns
Chart pattern recognition, price action patterns, candlestick signal bars, pullback bar counting H1/H2/H3/H4, trend channels, micro channels, trading ranges, breakouts, major trend reversals 5-step sequence, wedges, double tops and bottoms, triangles, head and shoulders, climaxes, measured moves, support and…
trade-execution
Trade execution using price action setups, major trend reversal trading top and bottom, MTR failure continuation, strong bull and bear breakout trading, strong and weak channel trading strategies, trading range strategies, opening range swings, integration with gold.technicalsetups for setup matching and execution…
challenge
Adversarial verification of research theses — cross-run/cross-thesis contradiction via the entity index, pre-mortem (Klarman/Kahneman: assume the loss already happened, reverse the path), inversion (Munger: invert, always invert), and wrongif falsifiability review. ≈50-finding cap sorted by severity; content-derived…
converge
Append-only gap closure and the cadence engine for research theses. Evaluates artifact CURRENT state (never git history, never task checkboxes) against current pins and wrongif falsifiers, then appends a Convergence section to tasks.md re-proposing the gaps. A clean run leaves tasks.md byte-identical. Deterministic…
constitution
Scaffold and amend the L1 Investment Constitution — [ALLCAPS] placeholder bootstrap, SemVer bump rules, Sync Impact Report, MINOR/MAJOR re-examination dispatch after the gate-5 budget confirm. Thesis creation stays refused until ratification (Q83).