Borrowing it
Nothing to install: this file belongs to pilinux/gorest. 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/pilinux/gorest/main/CLAUDE.mdgit clone --depth 1 https://github.com/pilinux/gorestWrote 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/pilinux/gorest/claude-md)<a href="https://agentmods.dev/instructions/pilinux/gorest/claude-md"><img src="https://agentmods.dev/badge/instructions/pilinux/gorest/claude-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.1 | $0.01079 | $0.01079 |
| Opus 5 | $0.00540 | $0.00540 |
| Sonnet 5 | $0.00216 | $0.00216 |
| Haiku 4.5 | $0.00108 | $0.00108 |
Grade A, and why
gorest CLAUDE.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 8d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Authoritative references
This repo already ships detailed agent docs. Read these before making changes — they are the source of truth and far more complete than this file:
AGENTS.md— build/lint/test commands, code style, import aliases, layer responsibilities, controller↔handler 1:1 map, config/db/middleware/service APIs.llms.txt— machine-readable interface describing repo purpose, capabilities, and constraints..agents/skills/<name>/SKILL.md— task-specific workflow guides (test-runner, ci-orchestrator, migration-helper, config-loader-helper, etc.).
Files to NEVER read or modify
Per .gitignore (and AGENTS.md), these contain secrets, keys, or generated noise.
Do not open, read, or edit them:
.envand any*.log(includeslog.txt),*.bakkeys/,tmp/,.build/,.vscode/,vendor/coverage.txt,coverage_0.txtpri*key*.pem,pub*key*.pemcrosscompile*.sh
Common commands
source setTestEnv.sh # required before running tests locally
go test -v -cover ./... # all tests
go test -v -run TestHashPass ./lib/... # single test function
golangci-lint run ./... # lint (CI uses v2.12.2, --timeout 5m)
go vet -v ./... && go build -v ./... # vet + build
CI additionally runs gosec, govulncheck, and cross-platform go vet/build across
linux/darwin/windows × amd64/arm64. Tests need env vars (CI uses secrets;
locally setTestEnv.sh).
Architecture (the big picture)
gorest is a reusable Go module (github.com/pilinux/gorest), not just an app. It is
both a library of auth/crypto/middleware/db primitives and two example apps that
wire them together. Requires Go 1.25.0+ (go.mod declares go 1.25.0; CI tests against Go 1.25.x and 1.26.x).
Request flow follows a strict layered pipeline:
controller/ → thin: bind request, call handler, renderer.Render(c, data, status)
handler/ → business logic + validation; returns (model.HTTPResponse, int)
service/ → shared utilities: auth, JWT blacklist, email (Postmark), crypto, 2FA
database/ → connection management for RDBMS (GORM), Redis (radix), MongoDB
config/ → loads .env → Configuration struct; IsX() feature toggles gate everything
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.
- 8d ago First seen · 88 lines · 1,079 tokens per session scan A 4f5d39605338
gorest CLAUDE.md is an instructions file published in the GitHub repository pilinux/gorest (504 stars, last pushed 3d ago), licensed MIT. It adds 1,079 tokens to every session, about $0.0054 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-30.
Other instructions, from other repositories
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.
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.
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).
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.