Borrowing it
Nothing to install: this file belongs to SVappsLAB/iRacingTelemetrySDK. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SVappsLAB/iRacingTelemetrySDK/main/AGENTS.mdgit clone --depth 1 https://github.com/SVappsLAB/iRacingTelemetrySDKWrote 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/instructions/svappslab/iracingtelemetrysdk/agents-md)<a href="https://agentmods.dev/instructions/svappslab/iracingtelemetrysdk/agents-md"><img src="https://agentmods.dev/badge/instructions/svappslab/iracingtelemetrysdk/agents-md.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.00664 | $0.00664 |
| Opus 5 | $0.00332 | $0.00332 |
| Sonnet 5 | $0.00133 | $0.00133 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
iRacingTelemetrySDK AGENTS.md 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 8d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file gives coding agents the repo-level context needed to work on iRacingTelemetrySDK.
For consumer-app usage patterns, read docs/ai/SDK_USAGE.md first and docs/ai/SDK_REFERENCE.md only for advanced scenarios.
Layout
Sdk/SVappsLAB.iRacingTelemetrySDK/- Core SDK, telemetry client, data providers, models, YAML parsing, and sim control (win32 broadcast commands).Sdk/SVappsLAB.iRacingTelemetrySDK.CodeGen/- Roslyn source generator for strongly typed telemetry records.Sdk/SVappsLAB.iRacingTelemetrySDK.EnumsAndFlags/- iRacing telemetry variable enums, flags, and related types.Sdk/tests/UnitTests/- Unit tests.Sdk/tests/SmokeTests/- IBT and live integration/smoke tests.Samples/- Example consumer applications.docs/ai/- Consumer-focused guidance for AI coding agents.
Commands
dotnet build .\Sdk\SVappsLAB.iRacingTelemetrySDK.slnx
dotnet build .\Samples\Samples.slnx
dotnet test --project .\Sdk\tests\UnitTests\UnitTests.csproj --no-build
dotnet run --project .\Sdk\tests\SmokeTests\SmokeTests.csproj -- --filter-trait Category=ibt
dotnet pack .\Sdk\SVappsLAB.iRacingTelemetrySDK\SVappsLAB.iRacingTelemetrySDK.csproj
Run Category=live smoke tests only with iRacing running in an active Windows session. Run Category=manual tests only when the local developer setup matches the test requirements.
global.json pins test.runner to Microsoft.Testing.Platform, so dotnet test needs --project/--solution (a bare positional path is rejected) and does not understand VSTest-style --filter. Use dotnet run --project, not dotnet test, for SmokeTests - its launchSettings.json injects a default --filter-class that dotnet test combines with (rather than overrides with) any --filter-trait you add, silently yielding "zero tests ran". See Sdk/tests/README.md for details.
Style
- Target .NET 8 for the SDK.
- Keep nullable annotations enabled and handle nullable telemetry values explicitly.
- Use a
TelemetryHandlers<TelemetryData>variable and pass it toMonitor(handlers, ct)for normal telemetry consumption. - Keep telemetry handlers fast, especially
OnTelemetryUpdateat 60 Hz. - Preserve public API docs when changing SDK contracts.
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.
- 8d ago First seen · 46 lines · 664 tokens per session scan A 64ef9af3b666
iRacingTelemetrySDK AGENTS.md is an instructions file published in the GitHub repository SVappsLAB/iRacingTelemetrySDK (25 stars, last pushed 9d ago), licensed Apache-2.0. It adds 664 tokens to every session, about $0.0033 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-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.