coverctl: Instructions file for Codex

AGENTS.md

coverctl AGENTS.md is an instructions file for Codex, OpenCode from klarlabs-studio/coverctl. It costs 746 tokens per session, scanned A, original, MIT.

Project instructions for the coverctl Go repository, including its folder structure, coding conventions, build commands, and testing rules. Go is a programming language, and coverctl checks test coverage, meaning how much code tests exercise.

In plain words
What is it for?
Building and testing coverctl, organizing code by responsibility, maintaining coverage configuration, and following the project's naming and review conventions.
Why use it?
It gives a coding agent the repository-specific rules needed to make compatible changes and run the right checks.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is klarlabs-studio/coverctl's own configuration. It tells Codex and OpenCode how to work on coverctl itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything coverctl configures →

Reuse

Borrowing it

Nothing to install: this file belongs to klarlabs-studio/coverctl. 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/klarlabs-studio/coverctl/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/klarlabs-studio/coverctl

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.

agentmods badge for coverctl AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/klarlabs-studio/coverctl/agents-md/github.svg)](https://agentmods.dev/instructions/klarlabs-studio/coverctl/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/klarlabs-studio/coverctl/agents-md"><img src="https://agentmods.dev/badge/instructions/klarlabs-studio/coverctl/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.

agentmods 80×15 button for coverctl AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/klarlabs-studio/coverctl/agents-md"><img src="https://agentmods.dev/badge/instructions/klarlabs-studio/coverctl/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 746 This file is loaded in full into every session.
When invoked 746 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00746 $0.00746
Opus 5.5 $0.00298 $0.00298
Sonnet 5.5 $0.00149 $0.00149
Haiku 4.5 $0.00075 $0.00075

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

Security

Grade A, and why

coverctl 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 1mo 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 · 42 lines

How it starts

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

Repository Guidelines

Intent. Read docs/strategy/system-intent.md before adding features. New work should make the autonomous coverage-governance loop (check → explain → suggest/debt → edit tests → check again) safer, faster, more deterministic, or more useful. Feature count is not a goal.

Project Structure & Module Organization

  • cmd/coverctl/ hosts the CLI entry point and wires infrastructure to application services.
  • internal/domain/, internal/application/, internal/infrastructure/ follow DDD: domain models contain rules, application orchestrates use cases, infrastructure provides adapters (config, Go tooling, reporting, coverprofile parsing).
  • schemas/ defines the .coverctl.yaml schema; relocate docs and fixtures near the packages they describe.
  • Keep generated folders (proto, mocks) tracked via the exclude list and review them with coverctl ignore before running policies.

Build, Test, and Development Commands

  • go test ./... runs the full suite.
  • go test -covermode=atomic -coverpkg=./cmd/... -coverpkg=./internal/... -coverprofile=.cover/coverage.out ./... mirrors the coverctl check instrumentation.
  • go run ./cmd/coverctl check enforces each domain's minimum from .coverctl.yaml (default 80%; some packages set explicit floors — see that file); repeat it after changing code or tests.
  • go run ./cmd/coverctl init launches the Bubble Tea wizard before writing .coverctl.yaml; pass --no-interactive for automation.
  • go run ./cmd/coverctl ignore lists the exclude patterns contributors already documented.
  • relicta release --yes (GitHub Action) builds the CLI artifact and publishes releases; see .relicta.yaml for details.

Coding Style & Naming Conventions

  • Format with gofmt, keep imports grouped, and prefer short, lowercase package names that mirror directories.
  • Name domain concepts clearly (PolicyEvaluator, CoverageReport); use table-driven tests for branching logic.
  • Keep CLI flags in kebab-case (e.g., --output json) and document them in README plus .coverctl.yaml.
  • Inject infrastructure implementations via constructors so DDD boundaries stay intact.

Read the full file on GitHub · 42 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.

  1. 1mo ago Changed · +5 lines · +66 tokens per session a4d4fb000b7a
  2. 2mo ago First seen · 37 lines · 680 tokens per session scan A e797294431c5

Subscribe to this mod's changes

coverctl AGENTS.md is an instructions file published in the GitHub repository klarlabs-studio/coverctl (1 stars, last pushed yesterday), licensed MIT. It adds 746 tokens to every session, about $0.0030 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.

Related

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

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

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

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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

microsoft/vscode · 2,750 tokens

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.

denoland/deno · 3,077 tokens