Borrowing it
Nothing to install: this file belongs to msenol/Gorev. 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/msenol/Gorev/main/AGENTS.mdgit clone --depth 1 https://github.com/msenol/GorevWrote 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/msenol/gorev/agents-md)<a href="https://agentmods.dev/instructions/msenol/gorev/agents-md"><img src="https://agentmods.dev/badge/instructions/msenol/gorev/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/msenol/gorev/agents-md"><img src="https://agentmods.dev/badge/instructions/msenol/gorev/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.00493 | $0.00493 |
| Opus 5.5 | $0.00197 | $0.00197 |
| Sonnet 5.5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
Gorev 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 2mo 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gorev Project - Agent Development Guide
Build/Lint/Test Commands
Go Server (gorev-mcpserver)
make build # Build for current platform
make test # Run all tests
make test-coverage # Run tests with coverage report
make fmt # Format code
make lint # Run golangci-lint
make deps # Download and tidy dependencies
go test -v ./... # Run all tests with verbose output
go test -v -run TestName # Run single test
VS Code Extension (gorev-vscode)
npm install # Install dependencies
npm run compile # Compile TypeScript
npm test # Run tests
npm run lint # Run ESLint
npm run package # Package extension
Root Project
make build # Build both modules
make test # Run all tests
make fmt # Format both modules
make lint # Lint both modules
make pre-commit # Run pre-commit checks
Code Style Guidelines
Go Code
- Imports: Group standard library, third-party, local packages
- Formatting: Use
make fmt(go fmt) - Naming: Turkish domain terms (gorev, proje), English technical terms
- Error Handling: Always return explicit errors, wrap with context
- i18n: Use
i18n.T("key", templateData)for user-facing strings - Testing: Use standardized
internal/testing/helpers.gopatterns
TypeScript Code
- Imports: Use ES6 imports, organize by type
- Formatting: TypeScript strict mode, ESLint configuration
- Naming: camelCase for variables, PascalCase for classes/interfaces
- Error Handling: Try-catch with proper error messages
- Testing: Mocha with Sinon mocks, 100% coverage required
Project Rules
- Rule 15 Compliance: NO workarounds, NO technical debt, NO quick fixes
- Template Usage: Mandatory for all task creation (v0.10.0+)
- Database: SQLite with migrations, workspace/global support
- Localization: Full TR/EN support with proper i18n keys
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.
- 2mo ago First seen · 63 lines · 493 tokens per session scan A 8ae990f1f759
Gorev AGENTS.md is an instructions file published in the GitHub repository msenol/Gorev (1 stars, last pushed 9mo ago), licensed MIT. It adds 493 tokens to every session, about $0.0020 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.