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/yaniv-golan/affinity-sdk/agents-mdgit clone --depth 1 https://github.com/yaniv-golan/affinity-sdkWrote 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/yaniv-golan/affinity-sdk/agents-md)<a href="https://agentmods.dev/instructions/yaniv-golan/affinity-sdk/agents-md"><img src="https://agentmods.dev/badge/instructions/yaniv-golan/affinity-sdk/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 | $0.01461 | $0.01461 |
| Opus 5 | $0.00731 | $0.00731 |
| Sonnet 5 | $0.00292 | $0.00292 |
| Haiku 4.5 | $0.00146 | $0.00146 |
Grade A, and why
affinity-sdk 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 3d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project Overview
affinity-sdk is a mixed Python monorepo centered on a strongly typed Affinity CRM SDK and CLI, with adjacent documentation, MCP server assets, and Claude Code plugin artifacts.
Primary components in this repository:
- SDK + CLI (Python package):
affinity/(published frompyproject.toml) - Test suite:
tests/(pytest, strict markers, async coverage) - Documentation source:
docs/public/(MkDocs Material) - MCP server distribution and tooling:
mcp/(versioned independently) - Claude Code plugin assets:
plugins/and.claude-plugin/
The project is configured for Python 3.10+ and emphasizes strict static analysis, clear API modeling, and automation-friendly CLI behavior.
Repository Structure
Top-level layout (validated paths):
affinity/— core SDK and CLI source codetests/— unit, integration, contract, and CLI-focused testsdocs/— docs sources and contributor guidesdocs/public/— MkDocs site content (mkdocs.ymluses this asdocs_dir)docs/cli-development-guide.md— CLI contribution guide
mcp/— MCP server runtime, scripts, docs, and versioning filesplugins/— plugin-related artifacts (SDK/CLI plugins).claude-plugin/— repository marketplace/plugin metadata.github/workflows/— CI and release automation workflowstools/— maintenance/release helper scripts
Important root files:
pyproject.toml— package metadata, dependencies, lint/type/test configmkdocs.yml— docs site navigation and build config.pre-commit-config.yaml— pre-commit hookscodecov.yml— coverage reporting configREADME.md— user-facing project overviewCONTRIBUTING.md— contributor workflowVERSIONING.md— release/version governance across SDK/MCP/pluginsCHANGELOG.md— SDK/CLI changelog
MCP-specific release/version files (validated):
mcp/VERSIONmcp/CHANGELOG.mdmcp/COMPATIBILITY
Development Guidelines
Environment and Installation
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.
- 3d ago First seen · 222 lines · 1,461 tokens per session scan A a3a34372661e
affinity-sdk AGENTS.md is an instructions file published in the GitHub repository yaniv-golan/affinity-sdk (0 stars, last pushed 1mo ago), licensed MIT. It adds 1,461 tokens to every session, about $0.0073 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
elnora-merit-aktiva AGENTS.md
AGENTS.md instructions for Elnora-AI/elnora-merit-aktiva, covering using elnora-merit from an agent, setup check, references & company profile, conventions and reading.
drogon-claude-plugin CLAUDE.md
Claude Code instructions for voidvec/drogon-claude-plugin, covering drogon 后端开发规则, a. 异步回调模型（所有 handler 的最高纪律）, b. 事件循环模型（trantor io）, skill 路由表 and 通用纪律（跨 skill）.
river-review GEMINI.md
Gemini CLI instructions for s977043/river-review, covering gemini instructions (river-review), 必須チェック, gemini-specific tips, prompt assembly and development tips.
ship-it open-pr.instructions.md
Instructions for khrichtchatyi/ship-it: When the user asks to open, create, or submit a pull request, follow the skill in skills/open-pr/SKILL.md in full: verify gh is authenticated, resolve the target repository and default branch, push the current branch, open one pull request with a title and body derived from the…
agent-skills CLAUDE.md
Instructions for mindbox-cloud/agent-skills, covering agent-skills — developer guide for claude code, repository purpose, repository structure, how to add a new plugin and step 1 — create the directory structure.
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).