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 instructions/kthy/felt-mcp/agents-mdgit clone --depth 1 https://github.com/kthy/felt-mcpWhat 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.00996 | $0.00996 |
| Opus 5 | $0.00498 | $0.00498 |
| Sonnet 5 | $0.00199 | $0.00199 |
| Haiku 4.5 | $0.00100 | $0.00100 |
Grade A, and why
felt-mcp 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 yesterday.
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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to AI agents working with code in this repository, which holds an MCP server for agentic interaction with [Felt]. More details in README.md.
Architecture Decision Records
Architecture decisions are documented in ADRs.md in the repository root. All code must adhere to the decisions recorded there.
Changelog
The project keeps a changelog in CHANGELOG.md. Usage is as described at https://keepachangelog.com/en/1.1.0/. You can also refer to https://raw.githubusercontent.com/Utiligize/configator-op/refs/heads/main/CHANGELOG.md to see how I want it to look.
SDK Docs
The MCP is built around the Felt API which has docs at https://developers.felt.com/rest-api/api-reference.
Commands
- Lint, format and type check:
just lint - Test:
just testor for single test:uv run python -m pytest tests/path/to/test.py::test_function - re-run previously failed tests:
just test-failed
Code Style Guidelines
- Python version: 3.14 (strict)
- Line length: 99 characters
- Indentation: 4 spaces for Python files
- Imports: Grouped by stdlib, third-party, local with alphabetical ordering
- Type hints: Required for all functions (
disallow_untyped_defs = true) - Naming: Follow Python conventions (snake_case for functions/variables, CamelCase for classes)
- Docstrings: Follow PEP 257 for concise, single-line docstrings for simple functions, more detailed for complex functionality
- Testing: Use pytest fixtures and appropriate mocking
- Formatting: Enforced by Ruff with rules listed in
pyproject.toml - Git commit messages: Use the Conventional Commits style
- When importing Python packages, use the explicit style
from <package> import <method>
MCP Tools & Configuration
- Context7: Use for up-to-date documentation for third-party code libraries
- SonarQube: See
sonar-project.propertiesfor project setup
Implementation Workflow
This repository follows GitHub Flow for version control and collaboration.
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.
- yesterday First seen · 123 lines · 996 tokens per session scan A f825abac7751
felt-mcp AGENTS.md is an instructions file published in the GitHub repository kthy/felt-mcp (0 stars, last pushed 5mo ago), licensed MIT. It adds 996 tokens to every session, about $0.0050 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
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.
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).
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.