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.
git clone --depth 1 https://github.com/dfirtnt/Huntable-CTI-StudioWrote 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/rules/dfirtnt/huntable-cti-studio/langchain-workflow-provider-agnostic)<a href="https://agentmods.dev/rules/dfirtnt/huntable-cti-studio/langchain-workflow-provider-agnostic"><img src="https://agentmods.dev/badge/rules/dfirtnt/huntable-cti-studio/langchain-workflow-provider-agnostic/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/rules/dfirtnt/huntable-cti-studio/langchain-workflow-provider-agnostic"><img src="https://agentmods.dev/badge/rules/dfirtnt/huntable-cti-studio/langchain-workflow-provider-agnostic.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.00354 |
| Opus 5 | $0.00000 | $0.00177 |
| Sonnet 5 | $0.00000 | $0.00071 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
langchain-workflow-provider-agnostic 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 11d 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.
What it actually says
Langchain Workflow — Provider-Agnostic Implementation
Changes to the LangGraph workflow and LLM service must work regardless of which model/provider is chosen (lmstudio, openai, anthropic).
Rules
-
No provider-specific branching — Do not add logic that only runs for one provider (e.g.
if provider == "openai"for behavior changes). Use the existingLLMServiceabstraction and_canonicalize_providerfor routing. -
Use config-driven provider/model — Read provider and model from
config_modelsorconfig_snapshot; never hardcode a provider or model name in workflow logic. -
Prompt and schema parity — Prompts, output schemas, and parsing must work across all providers. Avoid provider-specific prompt variants or response formats.
-
Parameter bounds — Temperature, max_tokens, and other inference params must use provider-agnostic defaults or provider-specific defaults from
provider_defaults; do not assume LMStudio-only semantics.
Examples
# ❌ BAD — provider-specific behavior
if provider == "lmstudio":
messages = build_messages_v1(prompt)
else:
messages = build_messages_v2(prompt)
# ✅ GOOD — single path for all providers
messages = build_messages(prompt)
# ❌ BAD — hardcoded model
model = "gpt-4o-mini"
# ✅ GOOD — from config/env
model = config_models.get("RankAgent") or self.provider_defaults.get(provider)
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.
- 11d ago First seen · 41 lines · 0 tokens per session scan A 1cfd6d861750
langchain-workflow-provider-agnostic is a cursor rule published in the GitHub repository dfirtnt/Huntable-CTI-Studio (11 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 354 tokens. 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-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.