What is gocron AGENTS.md?

Project instructions for gocron, a Go project whose development tools run through Docker Compose. They describe coding rules, generated files, commands, and pinned service versions.

Running formatting, code generation, tests, end-to-end tests, dependency commands, and rebuilds through the project's Docker setup.

They prevent developers from using mismatched host tools or editing files that are generated automatically, which can cause inconsistent builds and lost changes.

How flohoss/gocron configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to flohoss/gocron. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/flohoss/gocron/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/flohoss/gocron

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/flohoss/gocron/agents-md/github.svg)](https://agentmods.dev/instructions/flohoss/gocron/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/flohoss/gocron/agents-md"><img src="https://agentmods.dev/badge/instructions/flohoss/gocron/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/flohoss/gocron/agents-md"><img src="https://agentmods.dev/badge/instructions/flohoss/gocron/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,147 This file is loaded in full into every session.

When invoked 1,147 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01147	$0.01147
Opus 5.5	$0.00459	$0.00459
Sonnet 5.5	$0.00229	$0.00229
Haiku 4.5	$0.00115	$0.00115

Measured 14d ago against content hash b9dc10432c62, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gocron 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 14d 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.

AGENTS.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Guidance

Read before making changes. Rule-oriented and self-contained.

Principles

CLEAN code. Small functions, single responsibility, descriptive names, no dead code, no overengineering.
No comments. Use descriptive function or service names instead.
Test comments are allowed when the tested behaviour is not obvious from the test name: a short block above the test explaining what it asserts and why it exists.
No code markers like // ... existing code ... in edits.
Go imports: stdlib, then external, then internal (github.com/flohoss/gocron/...), each block alphabetical.
Never edit generated files (services/jobs/*.sql.go, models.go, web/src/client/).

Tooling — always via Docker Compose, never on the host

Code generation: docker compose run --rm backend sqlc generate
Backend format: docker compose run --rm go fmt ./...
Format (all non-Go files): docker compose run --rm format
Tests: docker compose run --rm go test ./...
Coverage: docker compose run --rm --entrypoint sh go coverage/coverage.sh — excludes generated files (detected by the // Code generated ... DO NOT EDIT. marker)
Coverage badge: docker compose run --rm --entrypoint sh go coverage/coverage-badge.sh — writes coverage/coverage.svg, which CI commits to main when the value changes

E2E tests (Headless):

docker compose -f compose.yml -f compose.e2e.yml --profile test run --rm e2e
# teardown when done:
docker compose -f compose.yml -f compose.e2e.yml --profile dev --profile test down

E2E interactive (Cypress GUI):

docker compose -f compose.yml -f compose.e2e.yml --profile dev --profile test up -d backend frontend
npm --prefix web/e2e run open
# teardown when done:
docker compose -f compose.yml -f compose.e2e.yml --profile dev --profile test down

Rebuild & reload: docker compose up

Only commit if format and tests pass.

Common Commands

docker compose run --rm npm install
docker compose run --rm --entrypoint npx npm --yes npm-check-updates -u && docker compose run --rm npm install
docker compose run --rm npm-e2e install
docker compose run --rm --entrypoint npx npm-e2e --yes npm-check-updates -u && docker compose run --rm npm-e2e install
docker compose run --rm go get -u ./...
docker compose run --rm go mod tidy
docker compose run --rm go fmt ./...

Read the full file on GitHub · 84 lines

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.

14d ago Changed · +1 lines · +21 tokens per session b9dc10432c62
20d ago Changed a556778dbb11
1mo ago Changed · +4 lines · +139 tokens per session f4465f30820c
1mo ago Changed · +15 lines · +226 tokens per session 5fd2f5d18331
2mo ago First seen · 64 lines · 761 tokens per session scan A 3ff6d671dfa8

Subscribe to this mod's changes

gocron AGENTS.md is an instructions file published in the GitHub repository flohoss/gocron (626 stars, last pushed 14d ago), licensed MIT. It adds 1,147 tokens to every session, about $0.0046 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-30.

Go backup backups cron docker schedule

gocron AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
gocron AGENTS.mdflohoss/gocron	Instructions file	626	14d ago	MIT	A	1,147	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

gocron: Instructions file for Codex