Borrowing it
Nothing to install: this file belongs to tecton-ai/tecton-mcp. 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/tecton-ai/tecton-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/tecton-ai/tecton-mcpWrote 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/tecton-ai/tecton-mcp/claude-md)<a href="https://agentmods.dev/instructions/tecton-ai/tecton-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/tecton-ai/tecton-mcp/claude-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.03875 | $0.03875 |
| Opus 5 | $0.01937 | $0.01937 |
| Sonnet 5 | $0.00775 | $0.00775 |
| Haiku 4.5 | $0.00387 | $0.00387 |
Grade A, and why
tecton-mcp CLAUDE.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 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.
How it starts
The opening of the file, as written. The whole thing — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Configuration for Tecton Feature Development
This file contains configuration and rules for Claude Code when working with Tecton feature repositories.
Tecton Feature Development Rules
General Feature Creation Guidelines
-
Break down feature implementation into stages:
- Fetch and review relevant rules
- Search for Tecton examples and API reference
- Look at existing feature repository for reusable Entities and Data Sources. If you find good fits, confirm with the user that they want to reuse.
- Implement the solution
-
CRITICAL: Before writing or editing feature code:
- You MUST call mcp_tecton_query_example_code_snippet_index_tool to look for relevant code snippets
- You MUST then think about all the available Tecton classes that you will use to implement the feature
- You MUST then call mcp_query_tecton_sdk_reference_tool to look at the exact definition of all the Tecton classes and functions you're planning to use
- You MUST finally come up with a plan that explains which parameters of BatchFeatureView, StreamFeatureView or RealTimeFeatureView you're planning to use based on the SDK reference
Feature View Selection Rules
- For aggregations over time windows ≤ 60 minutes, default to StreamFeatureView unless specified otherwise
- Never combine
AttributeandAggregatefeatures in the same FeatureView - Only supported
modevalues: "pyspark" and "spark_sql" (Rift not supported)
SQL Handling and Data Source References
- CRITICAL: If a user provides a SQL query for a feature: You MUST NOT translate the SQL logic into another language or API (e.g., PySpark DataFrames, Pandas) unless the user explicitly asks you to 'translate to PySpark' or 'rewrite using PySpark DataFrames'. Stick to SQL - it's ok to translate from say Snowflake SQL to Spark SQL if necessary.
- Be very thoughtful when you change a customer provided SQL statement. Make sure you don't remove anything that may be relevant to the feature transformation.
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.
- 7d ago First seen · 411 lines · 3,875 tokens per session scan A 98a056d9df96
tecton-mcp CLAUDE.md is an instructions file published in the GitHub repository tecton-ai/tecton-mcp (3 stars, last pushed 1y ago), licensed MIT. It adds 3,875 tokens to every session, about $0.0194 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 instructions, from other repositories
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).
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.
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.
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).
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.