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-pipelinegit 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-pipeline)<a href="https://agentmods.dev/skills/fusion-data-company/bristol-os/deal-pipeline"><img src="https://agentmods.dev/badge/skills/fusion-data-company/bristol-os/deal-pipeline/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-pipeline"><img src="https://agentmods.dev/badge/skills/fusion-data-company/bristol-os/deal-pipeline.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.00053 | $0.00611 |
| Opus 5.5 | $0.00021 | $0.00244 |
| Sonnet 5.5 | $0.00011 | $0.00122 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
deal-pipeline 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deal Pipeline
Keep a simple, living record of Bristol deals and produce clean status updates.
When to use
"Add this to my pipeline," "what's in the pipeline," "update [deal] to underwriting," "give me a pipeline summary for Monday."
Where it lives
A single file: bristol-os/pipeline.md in the workspace. Create it on first use.
Stages (Bristol deal lifecycle)
Sourced → Screening → Underwriting → IC/Approval → Capital Raise → Closing → Development → Lease-up → Stabilized → Disposition/Refi
For each deal track
- Name / location / product & units
- Stage + date entered stage
- Owner (who at Bristol is driving it)
- Next action + due date
- Key open items / blockers
- Link to the deal folder and latest memo
Operations
- Add: append a new deal row/section.
- Update: move stage, log the change with a date, update next action.
- Summary: produce a grouped-by-stage overview, highlight what's stalled (no movement / overdue next action) and what needs a decision.
- Whenever another play produces a deliverable for a deal, note it on that deal's pipeline entry.
Output
- Updated
pipeline.md, plus a readable summary when asked (e.g., a Monday update grouped by stage with a "needs your attention" section at top).
Live tracker artifact (build it for them — HARD LAW)
Bristol OS gives each person a live visual deal board they can reopen any time.
- The first time pipeline is used (and during onboarding), build it for them: read
bristol-os/templates/project-tracker.htmland create a persistent artifact from it with the create_artifact tool (title it "Bristol Deal Tracker"). Don't tell them how — just make it and open it. - Tell them where it is and how to use it in one plain sentence: "I made you a live Deal Tracker — it's pinned in this conversation; click any card to update a deal, and it saves itself on your computer."
- Keep it in sync: when a deal changes, update both
pipeline.mdand (when asked for the board) regenerate/refresh the artifact. The board saves deals in the browser, so it persists across sessions. - Never make the user build or find it themselves — you create it and point to 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.
- 1mo ago First seen · 46 lines · 53 tokens per session scan A df1e6b5b095e
deal-pipeline is a skill published in the GitHub repository Fusion-Data-Company/bristol-os (1 stars, last pushed 4mo ago), licensed MIT. It adds 53 tokens to every session and 611 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-08-31.
Other skills, from other repositories
procurement-optimizer
Use when running an annual SaaS audit, doing category-level spend review, or rationalizing the supplier base — when the user needs a spend audit, spend categorization (UNSPSC-aligned with Pareto breakdown and industry profiles), purchasing-cycle analysis (bottleneck categories per Goldratt's Theory of Constraints), or…
cwicr-schedule-integrator
Integrate CWICR cost data with project schedules. Link work items to schedule activities, generate cost-loaded schedules, and cash flow projections.
cash-flow-forecaster
Forecast project cash flow based on schedule and cost data. Generate S-curves and payment projections.
cashflow-forecaster
Forecast construction project cash flow. Project income and expenses, identify funding gaps, and optimize payment timing for improved financial management.
cwicr-change-order
Process construction change orders using CWICR data. Calculate cost impact, compare to original estimate, and generate change order documentation.
cwicr-subcontractor
Analyze and compare subcontractor bids against CWICR benchmarks. Evaluate pricing, identify outliers, and support negotiation.