blocker-scanner

blocker-scanner is a skill for Claude Code, Codex from violetfleming47/deal-intelligence. It costs 83 tokens per session (3,459 once invoked), scanned A, original, MIT.

A text-analysis procedure for finding signs that a sales deal is being slowed down or helped along. It reads meeting transcripts, customer-record notes, and sales emails to classify objections, competitive mentions, positive signals, and events that remove obstacles.

In plain words
What is it for?
Use it to scan customer and sales records for objections, friction, competitor references, boosts, and unblocking events, then write those classifications to the pipeline's designated data locations.
Why use it?
It turns unstructured sales conversations into consistent categories that a deal-intelligence system can use. This helps show why a deal may be stalling or progressing.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to scan customer and sales records for objections, friction, competitor references, boosts, and unblocking events, then write those classifications to the pipeline's designated data locations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/violetfleming47/deal-intelligence/blocker-scanner
Install

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.

Any agent
npx skills add violetfleming47/deal-intelligence --skill blocker-scanner
Clone the repo
git clone --depth 1 https://github.com/violetfleming47/deal-intelligence

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for blocker-scanner

README.md
[![agentmods](https://agentmods.dev/badge/skills/violetfleming47/deal-intelligence/blocker-scanner.svg)](https://agentmods.dev/skills/violetfleming47/deal-intelligence/blocker-scanner)
Your own site
<a href="https://agentmods.dev/skills/violetfleming47/deal-intelligence/blocker-scanner"><img src="https://agentmods.dev/badge/skills/violetfleming47/deal-intelligence/blocker-scanner.svg" alt="Measured on agentmods" height="20"></a>
Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,459 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00083 $0.03459
Opus 5 $0.00042 $0.01729
Sonnet 5 $0.00017 $0.00692
Haiku 4.5 $0.00008 $0.00346

Measured 7d ago against content hash 0f4dc9452705, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

blocker-scanner 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 7d 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.

skills/blocker-scanner/SKILL.md · 322 lines

How it starts

The opening of the file, as written. The whole thing — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Blocker Scanner — Objection & Friction/Boost Spotter

Also known as: Friction Reader (in pipeline diagrams)

Adapting this skill: All CRM-specific values are wrapped in {{PLACEHOLDER}} markers. Before deploying, pull your CRM and transcript provider schemas (see guides/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 loads F09 and the supabase-reading-guide from the frameworks database. In the starter, these queries return empty results. The skill detects friction patterns using F07 and its built-in pattern library. F09 adds industry-specific regulatory vocabulary when present but is not required.

You are the Blocker Scanner for {{COMPANY_NAME}}'s Deal Intelligence pipeline. You read unstructured text and classify what is accelerating or stalling each deal — friction events, objections, competitive mentions, boosts, and unblocking events. You are one of six spotters that run in parallel.

Boundary

You answer one question: What friction and boost signals are present in the conversations around each deal?

You do NOT:

  • Classify deal progression signals (Activation, Commitment, etc.). That is the Conversation Reader's job (F02).
  • Classify F03 stakeholder roles. That is the Stakeholder Reader's job (full system). In the starter, the Assembler builds titles_state from contact data without role classification.
  • Measure engagement cadence. That is the Cadence Reader's job.
  • Assess friction persistence or resolution across versions. That is pattern engine territory (Phase 3).
  • Write to di_deal_state. You write to di_raw_signals, di_signal_classifications, di_traceability_log, and di_scratchpad only.

Framework Loading

Load each framework individually (single query per framework to avoid MCP response size limits):

SELECT content, version FROM di_frameworks WHERE framework_id = 'F07' AND status = 'active';
SELECT content, version FROM di_frameworks WHERE framework_id = 'F09' AND status = 'active';
SELECT content, version FROM di_frameworks WHERE framework_id = 'F02' AND status = 'active';
SELECT content, version FROM di_frameworks WHERE framework_id = 'supabase-reading-guide' AND status = 'active';

Read the full file on GitHub · 322 lines

Changes

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.

  1. 7d ago First seen · 322 lines · 83 tokens per session scan A 0f4dc9452705

Subscribe to this mod's changes

blocker-scanner is a skill published in the GitHub repository violetfleming47/deal-intelligence (5 stars, last pushed 4mo ago), licensed MIT. It adds 83 tokens to every session and 3,459 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.