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/msenol/gorev/agents-mdgit clone --depth 1 https://github.com/msenol/GorevWhat 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.00493 | $0.00493 |
| Opus 5 | $0.00246 | $0.00246 |
| Sonnet 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 2d 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.
- 2d 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 7mo ago), licensed MIT. It adds 493 tokens to every session, about $0.0025 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
graymatter AGENTS.md
Instructions for angelnicolasc/graymatter, covering agents.md, your tools, when to call which, first call and identity.
graymatter CLAUDE.md
Instructions for angelnicolasc/graymatter, covering claude.md, a user asked you to set graymatter up, you are working in a project that already uses graymatter and you are contributing to graymatter itself.
calva-backseat-driver AGENTS.md
Instructions for BetterThanTomorrow/calva-backseat-driver, covering calva backseat driver - ai agent guide, essential architecture, action/effect system ("ex"), runtime state structure and datascript connections.
calva-backseat-driver backseat-driver-source-conventions.instructions.md
Backseat Driver extension source code conventions — Ex framework patterns, async, state management, namespace separation, and naming. Supplements universal Clojure patterns with Backseat Driver-specific rules.
calva-backseat-driver copilot-instructions.md
Instructions for BetterThanTomorrow/calva-backseat-driver, covering what backseat driver is, repl environment, state inspection safety, bundled ai context (chatskills / chatinstructions) and key development commands.
calva-backseat-driver changelog.instructions.md
CHANGELOG.md conventions — audience, scope, and entry format for the Backseat Driver extension changelog.