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/CiscoDevNet/essentialsWrote 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/ciscodevnet/essentials/langsmith)<a href="https://agentmods.dev/rules/ciscodevnet/essentials/langsmith"><img src="https://agentmods.dev/badge/rules/ciscodevnet/essentials/langsmith.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.1 | $0.00285 | $0.00285 |
| Opus 5 | $0.00143 | $0.00143 |
| Sonnet 5 | $0.00057 | $0.00057 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
langsmith 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 2d 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
LangSmith Naming Convention
The LangChain company has rebranded around LangSmith. When choosing names for resources, variables, comments, or documentation:
- Use "langsmith" (or "LangSmith") as the prefix/brand, not "langgraph".
- Drop prefixes entirely when the context already implies LangSmith (e.g., inside a
langsmith-hostingpackage, usedataplanenotlangsmith-dataplane).
What you CAN rename
- Pulumi resource names (
f"{cluster_name}-dataplane") - Helm release names (
name="dataplane") - Comments, docstrings, and documentation
- Variable names, constant names, file names
What you CANNOT rename
Values that are API contracts controlled by upstream (LangChain's Helm repo, REST APIs):
- Helm chart names (
chart="langgraph-dataplane"-- published chart name) - Helm values schema keys (
"langgraphListenerId"-- expected by the chart) - API endpoint paths and request/response field names
- CRD names (
lgps.apps.langchain.ai)
When an upstream contract uses "langgraph", keep it as-is and add a brief inline note if clarity helps.
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.
- 2d ago First seen · 30 lines · 285 tokens per session scan A e8e9431e1cc5
langsmith is a cursor rule published in the GitHub repository CiscoDevNet/essentials (7 stars, last pushed 18d ago), licensed Apache-2.0. It adds 285 tokens to every session, about $0.0014 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-09-04.
Other cursor rules, from other repositories
solar
Rules for building with Solar (solarbuild) — a runtime UI framework for AI-generated code.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .
no-family-vocabulary-in-framework
The framework domain (packages/1-framework) carries no family- or target-specific vocabulary — types, fields, hooks, or strategy values. Enforced by the no-family-vocabulary Biome plugin plus lint:framework-vocabulary.
use-contract-ir-factories
Use factory functions for creating ContractIR objects instead of manual object creation.
no-barrel-files
Avoid barrel files and unnecessary re-exports.