gitcontribute: Instructions file for Codex

AGENTS.md

gitcontribute AGENTS.md is an instructions file for Codex, OpenCode from morluto/gitcontribute. It costs 463 tokens per session, scanned A, original, MIT.

A repository guide that tells coding agents how to work in the GitContribute codebase, including its goals, boundaries, and engineering rules. GitContribute is a local research and validation workspace that keeps repository and GitHub context explicit.

In plain words
What is it for?
Use it when contributing to GitContribute, especially when changing its architecture, MCP integration, or evidence records. It helps agents follow repository agreements and distinguish imported claims from locally reproduced evidence.
Why use it?
It gives agents shared project context and prevents them from treating missing or outdated information as proof that something does not exist. It also clarifies which actions, such as network access or GitHub changes, must remain explicit.

Instructions file for CodexOpenCode

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

This is morluto/gitcontribute's own configuration. It tells Codex and OpenCode how to work on gitcontribute 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 gitcontribute configures →

Reuse

Borrowing it

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

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 gitcontribute AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/morluto/gitcontribute/agents-md"><img src="https://agentmods.dev/badge/instructions/morluto/gitcontribute/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 463 This file is loaded in full into every session.
When invoked 463 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.00463 $0.00463
Opus 5.5 $0.00185 $0.00185
Sonnet 5.5 $0.00093 $0.00093
Haiku 4.5 $0.00046 $0.00046

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

Security

Grade A, and why

gitcontribute 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 2mo 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 · 50 lines

How it starts

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

Repository working agreements

What we are building

GitContribute is a local-first research and validation workbench for coding agents. It gives agents durable repository and GitHub facts, bounded acquisition and workspace capabilities, and source-bound validation evidence. Agents do the reasoning and contribution work; GitContribute provides the trustworthy local context and explicit capabilities they need. It does not hide network access, process execution, local writes, or GitHub mutation inside reads.

Treat missing, stale, incomplete, or superseded coverage as unknown rather than as negative evidence. Keep imported external claims distinct from validation reproduced by GitContribute. For the detailed contracts, read docs/architecture.md, CONTRIBUTING.md, and, for MCP or evidence changes, docs/mcp.md and docs/external-evidence-manifests.md.

Product boundaries

  • Follow the contracts in docs/architecture.md; do not preserve Gitcrawl compatibility.
  • Do not import Gitcrawl or Crawlkit modules.
  • Prefer the standard library or mature maintained packages over custom protocol, migration, authentication, concurrency, and terminal machinery.
  • Keep third-party types inside adapters. Domain and application contracts are owned by this repository.
  • When copying third-party source, preserve notices required by its license with the adapted source or under LICENSES/.

Side effects

  • Corpus reads must not perform network access.
  • GitHub access, local writes, process execution, and external mutations are separate capabilities.
  • No GitHub mutation is in scope unless explicitly approved.
  • Never execute repository-controlled code during crawling or indexing.

Engineering rules

  • Keep packages focused and interfaces narrow; avoid config bags and mode booleans.
  • Pass context.Context through I/O and long-running operations.
  • Make acquisition, sync, indexing, and projection writes idempotent; prevent stale observations from replacing newer projections.
  • Replace child snapshots atomically only after complete retrieval.
  • Run gofmt on changed Go files and focused tests while working; run make verify before opening a pull request.
  • Add focused regression tests for ordering, resumability, cancellation, and side-effect boundaries.

Read the full file on GitHub · 50 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. 2mo ago First seen · 50 lines · 463 tokens per session scan A 68587f58a8b9

Subscribe to this mod's changes

gitcontribute AGENTS.md is an instructions file published in the GitHub repository morluto/gitcontribute (28 stars, last pushed 1mo ago), licensed MIT. It adds 463 tokens to every session, about $0.0019 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