Borrowing it
Nothing to install: this file belongs to brazilofmux/gnucobol. 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/brazilofmux/gnucobol/master/AGENTS.mdgit clone --depth 1 https://github.com/brazilofmux/gnucobolWrote 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/brazilofmux/gnucobol/agents-md)<a href="https://agentmods.dev/instructions/brazilofmux/gnucobol/agents-md"><img src="https://agentmods.dev/badge/instructions/brazilofmux/gnucobol/agents-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.00584 | $0.00584 |
| Opus 5 | $0.00292 | $0.00292 |
| Sonnet 5 | $0.00117 | $0.00117 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
gnucobol 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 6d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
This repository wraps multiple GnuCOBOL releases as container builds.
3.0/,3.1/,3.2/,4.0/: versioned container stacks withbuilder/,runtime/,hello/, and a localdaily.sh.*/builder/Dockerfile: builds the compiler image from the packaged source tarball.*/runtime/Dockerfile: trims the runtime dependencies for compiled COBOL programs.*/hello/test.cob: minimal smoke-test program used by the hello image.daily.shandupdate.sh: reference scripts that document the release/update flow more than day-to-day development.
Build, Test, and Development Commands
cd 4.0 && ./daily.sh: buildgnucobol:4.0-builder,gnucobol:4.0-runtime, andgnucobol:4.0-hellowithpodman.cd 4.0/builder && podman build -t gnucobol:4.0-builder .: rebuild one image while iterating on a Dockerfile.cd 4.0/hello && podman build -t gnucobol:4.0-hello .: rebuild the smoke-test image after editingtest.cob.cd 4.0/runtime && podman build -t gnucobol:4.0-runtime .: validate runtime-layer changes in isolation.
Coding Style & Naming Conventions
Follow the style already in the tree.
- Use 4-space indentation in shell scripts and keep loops/simple command sequences compact.
- Preserve the existing split between
builder,runtime, andhellounder each version directory. - Keep COBOL examples minimal and readable; the current
test.cobfiles use classic uppercase COBOL formatting. - Prefer small, targeted edits and keep version-specific changes isolated to the matching directory.
Testing Guidelines
There is no separate test framework in this repository; validation is build-based.
- Rebuild the affected container stack with
./daily.shafter changing Dockerfiles or version scripts. - Rebuild the specific
helloimage if you change a sample program or compiler flags. - Treat a clean
podman buildand a working hello image as the minimum acceptance bar.
Commit & Pull Request Guidelines
Recent history favors short, imperative commit subjects such as Fix build again and Add update.sh.
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.
- 6d ago First seen · 40 lines · 584 tokens per session scan A 605a5fa4770c
gnucobol AGENTS.md is an instructions file published in the GitHub repository brazilofmux/gnucobol (5 stars, last pushed 22d ago), licensed MIT. It adds 584 tokens to every session, about $0.0029 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
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.
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).
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).
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.
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.