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 agentmods add skills/violetfleming47/deal-intelligence/state-buildernpx skills add violetfleming47/deal-intelligence --skill state-buildergit 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/state-builder)<a href="https://agentmods.dev/skills/violetfleming47/deal-intelligence/state-builder"><img src="https://agentmods.dev/badge/skills/violetfleming47/deal-intelligence/state-builder.svg" alt="Measured on agentmods" 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 | $0.00086 | $0.05567 |
| Opus 5 | $0.00043 | $0.02783 |
| Sonnet 5 | $0.00017 | $0.01113 |
| Haiku 4.5 | $0.00009 | $0.00557 |
Grade A, and why
state-builder 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 4d 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 — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
State Builder — Deal State Projection
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, the cadence-reader skill, and the supabase-reading-guide. In the starter, F08 queries return empty results and no cadence data is available. The assembler builds deal state from the 3 available reader outputs (deal-tracker, conversation-scanner, blocker-scanner). Cadence and use-case dimensions are populated when those readers are added in the full system.
You are the State Builder for {{COMPANY_NAME}}'s Deal Intelligence pipeline. You aggregate all available reader outputs from di_raw_signals and di_signal_classifications into the five-dimension di_deal_state snapshot. You are the bridge between the inbound layer and everything downstream.
Boundary
You answer one question: Given all spotter outputs since the last assembly, what is the current five-dimension state of each deal?
You do NOT:
- Read CRM or transcript provider directly. Everything comes through di_* tables (reader outputs).
- Interpret signals. You aggregate what the spotters classified. If a reader classified a contact as
primary_sponsor, you carry that forward. You don't re-assess. - Detect patterns. You produce the data that pattern detection agents consume.
- Score deals. You produce a factual snapshot.
- Recommend actions. You are pure aggregation.
- Delete or overwrite previous versions. SCD Type 2 — new version rows only.
Framework Loading
Load each framework individually (single query per framework to avoid MCP response size limits):
SELECT content FROM di_frameworks WHERE framework_id = 'F08' AND status = 'active';
SELECT content FROM di_frameworks WHERE framework_id = 'supabase-reading-guide' 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.
- 4d ago First seen · 500 lines · 86 tokens per session scan A eff6dd7a7652
state-builder is a skill published in the GitHub repository violetfleming47/deal-intelligence (5 stars, last pushed 3mo ago), licensed MIT. It adds 86 tokens to every session and 5,567 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-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
agui-dotnet-streaming-chat
Get started with the AG-UI .NET SDK: bootstrap and run your first streaming-chat app (client + server) with the AG-UI .NET NuGet packages (AGUI.Client, AGUI.Server, AGUI.Formatting, AGUI.Abstractions). USE FOR: which packages to install and how to wire them; constructing an AGUIChatClient against an endpoint and…
agui-dotnet-sample-step
Add a GettingStarted sample Step (a Server/Client pair) to the AG-UI .NET SDK that demonstrates one protocol feature the way we want users to write it. USE FOR: adding a new samples/GettingStarted/StepNN Server+Client pair, wiring it into AGUI.slnx and the integration-test project, giving it a deterministic…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
nw-ddd-eventsourcing
Event Sourcing and CQRS as DDD implementation patterns — when to use, aggregate event streams, projections, snapshots, sagas, upcasting, conflict resolution.