Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/morluto/gitcontribute/agents-mdgit clone --depth 1 https://github.com/morluto/gitcontributeWhat 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 | $0.00463 | $0.00463 |
| Opus 5 | $0.00231 | $0.00231 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00046 | $0.00046 |
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 yesterday.
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 — 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.Contextthrough 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
gofmton changed Go files and focused tests while working; runmake verifybefore opening a pull request. - Add focused regression tests for ordering, resumability, cancellation, and side-effect boundaries.
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.
- yesterday First seen · 50 lines · 463 tokens per session scan A 68587f58a8b9
gitcontribute AGENTS.md is an instructions file published in the GitHub repository morluto/gitcontribute (3 stars, last pushed 2d ago), licensed MIT. It adds 463 tokens to every session, about $0.0023 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
EchoBird AGENTS.md
Instructions for edison7009/EchoBird, covering agents.md — echobird, project shape, ci gates (must pass locally before pushing), lesson (learned the hard way) and verification habits.
Agentkey AGENTS.md
Instructions for chainbase-labs/Agentkey, covering agents.md, what this repo is, directory structure, key commands and test a local edit against every detected agent.
superdesign-skill AGENTS.md
Instructions for superdesigndev/superdesign-skill, covering project agent memory, what this repo is, skill flow invariant: two entry paths, ground truth for cli behavior and plugin packaging & release.
seektty AGENTS.md
Instructions for Hilbert-beinghappy/seektty: This repository ships one out-of-tree DeepSeek Harness Bundle. Harness remains the only owner of Agent, Session, model, settings, permissions, Profile, plugin, and persistence state.
causal-memory CLAUDE.md
Instructions for JingxuanC/causal-memory, covering causal memory mcp integration, causal memory integration, after acting on a decision and observing the result, when something fails unexpectedly and when a recorded lesson turns out to be wrong.
dsh-deepread AGENTS.md
Instructions for xiehuan123/dsh-deepread, covering agents.md, upstream authority, plugin identities and source files, release documentation and harness lifecycle rules.