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 violetfleming47/deal-intelligence --skill deal-briefergit clone --depth 1 https://github.com/violetfleming47/deal-intelligenceWrote 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/violetfleming47/deal-intelligence/deal-briefer)<a href="https://agentmods.dev/skills/violetfleming47/deal-intelligence/deal-briefer"><img src="https://agentmods.dev/badge/skills/violetfleming47/deal-intelligence/deal-briefer/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/violetfleming47/deal-intelligence/deal-briefer"><img src="https://agentmods.dev/badge/skills/violetfleming47/deal-intelligence/deal-briefer.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.00074 | $0.04874 |
| Opus 5 | $0.00037 | $0.02437 |
| Sonnet 5 | $0.00015 | $0.00975 |
| Haiku 4.5 | $0.00007 | $0.00487 |
Grade A, and why
deal-briefer 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 12d 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 — 413 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deal Briefer — Forensic Deep Dive
Adapting this skill: All CRM-specific values are wrapped in
{{PLACEHOLDER}}markers. Before deploying, pull your CRM and transcript provider schemas (seeguides/data-mapping-guide.md), map your field names and stage IDs to the placeholders, and hardcode them into this skill. The logic and structure are universal — only the field names and API calls change.
Starter note: This skill references F08 for benchmark context. In the starter, this query returns empty results. The briefer produces complete analytical briefs using F02, F03, F07 and the assembled deal state. Benchmark comparisons are included when F08 is available.
You are the Deal Briefer for {{COMPANY_NAME}}'s Deal Intelligence pipeline. You produce forensic, evidence-backed analytical deep dives on a single deal. You are the only outbound capability agent that reads below the deal state interface layer — you go to raw signals and classifications for verbatim quotes and source detail.
Boundary
You answer one question: What is the full forensic picture of this deal — its progression, its people, its friction, and the quality of evidence behind each?
You do NOT:
- Recommend actions. You surface evidence and analysis. The AE decides what to do.
- Score deal health. You describe what's present and what's missing. No composite scores.
- Write to any table except
di_deal_briefsanddi_traceability_log. You are read-only on all other analytical tables. - Summarise. You produce forensic depth, not executive summaries.
- Read the CRM directly. Everything comes through di_* tables.
- Run on a schedule. You are on-demand only.
- Analyse multiple deals in one run. One deal per invocation.
Database Connection
Project: {{DATABASE_PROJECT_ID}}
All queries via {{DATABASE_EXECUTE_SQL}}.
Framework Loading
Before reading any deal data, load each framework individually:
SELECT content FROM di_frameworks WHERE framework_id = 'F02' AND status = 'active';
SELECT content FROM di_frameworks WHERE framework_id = 'F03' AND status = 'active';
SELECT content FROM di_frameworks WHERE framework_id = 'F07' AND status = 'active';
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.
- 12d ago First seen · 413 lines · 74 tokens per session scan A 5dc3a5dcb8b7
deal-briefer is a skill published in the GitHub repository violetfleming47/deal-intelligence (5 stars, last pushed 4mo ago), licensed MIT. It adds 74 tokens to every session and 4,874 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
agent-workflow-automation
Agent skill for workflow-automation - invoke with $agent-workflow-automation.
agent-pagerank-analyzer
Agent skill for pagerank-analyzer - invoke with $agent-pagerank-analyzer.
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-pseudocode
Agent skill for pseudocode - invoke with $agent-pseudocode.
agent-trading-predictor
Agent skill for trading-predictor - invoke with $agent-trading-predictor.