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 w95/awesome-claude-corporate-skills --skill deal-trackergit clone --depth 1 https://github.com/w95/awesome-claude-corporate-skillsWrote 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/w95/awesome-claude-corporate-skills/deal-tracker)<a href="https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/deal-tracker"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/deal-tracker/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/w95/awesome-claude-corporate-skills/deal-tracker"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/deal-tracker.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.00000 | $0.00770 |
| Opus 5 | $0.00000 | $0.00385 |
| Sonnet 5 | $0.00000 | $0.00154 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
deal-tracker 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 13d 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.
This is a copy
97% identical to deal-tracker — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deal Tracker
description: Track multiple live deals with milestones, deadlines, action items, and status updates. Maintains a deal pipeline view and surfaces upcoming deadlines and overdue items. Use when managing a book of business, tracking process milestones, or preparing for weekly deal reviews. Triggers on "deal tracker", "deal status", "where are we on", "process update", "deal pipeline", or "weekly deal review".
Workflow
Step 1: Deal Setup
For each deal, capture:
- Deal name / code name: Project [Name]
- Client: Seller or buyer name
- Deal type: Sell-side, buy-side, financing, restructuring
- Role: Lead advisor, co-advisor, fairness opinion
- Deal size: Expected enterprise value
- Stage: Pre-mandate → Engaged → Marketing → IOI → Diligence → Final bids → Signing → Close
- Team: MD, VP, Associate, Analyst assigned
- Key dates: Engagement date, CIM distribution, IOI deadline, management meetings, final bid deadline, target close
Step 2: Milestone Tracking
Track key milestones per deal:
| Milestone | Target Date | Actual Date | Status | Notes |
|---|---|---|---|---|
| Engagement letter signed | ||||
| CIM / teaser drafted | ||||
| Buyer list approved | ||||
| Teaser distributed | ||||
| NDA execution | ||||
| CIM distributed | ||||
| IOI deadline | ||||
| IOIs received / reviewed | ||||
| Shortlist selected | ||||
| Management meetings | ||||
| Data room opened | ||||
| Final bid deadline | ||||
| Bids received / reviewed | ||||
| Exclusivity granted | ||||
| Confirmatory diligence | ||||
| Purchase agreement signed | ||||
| Regulatory approval | ||||
| Close |
Status: On Track / At Risk / Delayed / Complete
Step 3: Action Items
Maintain a running action item list across all deals:
| Action | Deal | Owner | Due Date | Priority | Status |
|---|---|---|---|---|---|
| P0/P1/P2 | Open/Done/Blocked |
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.
- 13d ago First seen · 88 lines · 0 tokens per session scan A bb18f9ba6ae1
deal-tracker is a skill published in the GitHub repository w95/awesome-claude-corporate-skills (198 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 770 tokens. A static security scan graded it A with 0 findings. It is 97% identical to deal-tracker, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
workflow
Starts and manages autonomous agent workflows. Triggers: workflow, start workflow, autonomous agents, agent pipeline.
autonomous-dev
Drives a brief, specification, issue or existing PR through implementation, review, tests and QA to a ready PR. Persists ownership, progress and commit-bound evidence for safe resumption. Use for autonomous software delivery or finishing an interrupted development run.
onboard
Sets up ai-toolkit in a project: symlinks, CLAUDE.md, intent interview. Triggers: onboard, setup project, install ai-toolkit, migrate project.
plan
Breaks features/goals into phased plans with task lists, agent assignments, dependencies. Triggers: plan feature, implementation roadmap, break down task, project phases.
prd-to-issues
Splits a PRD into vertical-slice GitHub issues with HITL/AFK tagging and dependencies. Triggers: PRD to issues, create tickets, break down PRD, work items.
prd-to-plan
Converts PRD into phased plan via tracer-bullet vertical slices. Triggers: PRD to plan, break down PRD, implementation plan, tracer bullets, phased plan.