Borrowing it
Nothing to install: this file belongs to codeready-toolchain/tarsy. 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/codeready-toolchain/tarsy/master/AGENTS.mdgit clone --depth 1 https://github.com/codeready-toolchain/tarsyWrote 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/codeready-toolchain/tarsy/agents-md)<a href="https://agentmods.dev/instructions/codeready-toolchain/tarsy/agents-md"><img src="https://agentmods.dev/badge/instructions/codeready-toolchain/tarsy/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/codeready-toolchain/tarsy/agents-md"><img src="https://agentmods.dev/badge/instructions/codeready-toolchain/tarsy/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00561 | $0.00561 |
| Opus 5.5 | $0.00224 | $0.00224 |
| Sonnet 5.5 | $0.00112 | $0.00112 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
tarsy 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 today.
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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TARSy - agent guide
TARSy is a hybrid Go + Python SRE system: Go orchestrator (alerts, sessions, MCP tools), a stateless Python LLM service over gRPC, and a React dashboard.
Default branch: master. Architecture and package map: CLAUDE.md.
Commands
Never invent alternate package-manager commands if these work.
- Full local gate:
make check-all - Lint:
make lint(make lint-fixto auto-fix) - Test:
make test - Format:
make fmt - Dev:
make doctor,make setup,make dev,make dev-stop - Go:
make test-unit,make test-go,make build - Python LLM service:
make test-llm - Dashboard:
make test-dashboard - Codegen:
make ent-generate,make proto-generate - Migrations:
make migrate-create NAME=add_feature— then apply thedb-migration-reviewskill - LLM image deps: after changing
llm-service/uv.lock, runmake llm-requirements
Skills
Project skills live in .cursor/skills/ (symlinked as .claude/skills/). Load a skill when its description matches the task. Do not preload all of them.
How we work
- Don't assume; surface tradeoffs and ask when unclear
- Minimum code that solves the problem; no speculative features or abstractions
- Touch only what you must; no drive-by refactors
- Define success criteria and verify before finishing
Commits and PRs
- Never commit, amend, or push unless the user explicitly asks in this turn
- “Make the change”, “fix the tests”, or finishing a task is not permission to commit
- If it is unclear, leave changes uncommitted and ask
- Conventional commits:
build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test(scope): summary - Prefer small, focused PRs
- Fixes should reference an issue:
Fixes #123
Style
- Match existing code; do not reformat unrelated files
- Prefer clear names over clever abstractions
- No AI walls of text in PR descriptions
Safety
- Do not commit secrets
- Do not weaken CI, auth, or permission checks without an explicit human request
- Ask before large architectural changes
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.
- today Changed · +11 tokens per session fc6346cfdcb1
- 1mo ago First seen · 58 lines · 550 tokens per session scan A 06c3072c46b6
tarsy AGENTS.md is an instructions file published in the GitHub repository codeready-toolchain/tarsy (10 stars, last pushed today), licensed Apache-2.0. It adds 561 tokens to every session, about $0.0022 per session on Opus 5.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
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.