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/trenza1ore/gitcode-api/agents-mdgit clone --depth 1 https://github.com/Trenza1ore/GitCode-APIWhat 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.03160 | $0.03160 |
| Opus 5 | $0.01580 | $0.01580 |
| Sonnet 5 | $0.00632 | $0.00632 |
| Haiku 4.5 | $0.00316 | $0.00316 |
Grade A, and why
GitCode-API 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 2d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI agents working in this repository.
Project Overview
gitcode-api is a community-maintained Python SDK for the GitCode REST API. It exposes synchronous and asynchronous httpx clients, resource-oriented helpers such as client.repos and client.pulls, lightweight response models, a small CLI, examples, and Sphinx documentation. Optional LLM / agent helpers live under gitcode_api.llm (OpenAI Chat Completions tool shape, MCP via FastMCP) with lazy imports so the core install stays light.
Primary source paths:
gitcode_api/: package source.gitcode_api/_client.py: top-levelGitCodeandAsyncGitCodeclients.gitcode_api/_base_client.py: shared transport, auth, URL building, payload cleanup, response parsing, and context-manager behavior.gitcode_api/_base_resource.py: shared resource introspection (methods,method_signature).gitcode_api/resources/: sync and async REST resource groups.gitcode_api/_models.py: dictionary-backed response models and typed parameter payloads.gitcode_api/llm/: optional adapters —GitCodeOpenAITool,GitCodeMCP,create_openjiuwen_gitcode_api_tool(openJiuwenLocalFunction, requiresopenjiuwenon Python 3.11+),create_mcp_*/register_mcp_*/create_mcp_server; shared logic ingitcode_api/llm/_tool.py(GitCodeLLMTool). Public names load lazily throughgitcode_api.llm.__getattr__.gitcode_api/cli.py: installed CLI entry point, exposed asgitcode-api.tests/: unit tests and docs-backed endpoint/response checks.docs/: Sphinx documentation.examples/: runnable examples that read configuration fromexamples/.env.
Ignore generated or build output as source of truth, especially build/, dist/, docs/_build/, docs/_downloads/, and docs/sdk/generated/.
Tooling And Commands
Use uv from the repository root.
- Install/sync development dependencies:
uv sync --all-groups. - Run tests:
uv run pytestormake test. - Run a focused test:
uv run pytest tests/test_client.py -k context_manager. - Format and fix imports:
make format. - Type-check the package:
make lint(mypy -p gitcode_api). - Check docstrings:
make docstring. - Build docs:
make docs-dev(this also runs reST table alignment fixing). - Build a standalone CLI binary (PyInstaller one-file):
make binary(uses dependency groupbinary; output underdist/).
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.
- 2d ago First seen · 181 lines · 3,160 tokens per session scan A 98c4d9f58143
GitCode-API AGENTS.md is an instructions file published in the GitHub repository Trenza1ore/GitCode-API (7 stars, last pushed 1mo ago), licensed MIT. It adds 3,160 tokens to every session, about $0.0158 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
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
InvestSkill GEMINI.md
Instructions for yennanliu/InvestSkill, covering investskill — gemini cli setup & usage guide, installation & setup, quick start, navigate to the investskill directory and start gemini cli (loads gemini.md automatically).
she-love-me CLAUDE.md
Instructions for 863401402/she-love-me, covering claude.md and 唯一工作流.
wayland-core copilot-instructions.md
Instructions for FerroxLabs/wayland-core, covering ijfw rules, output discipline, memory routing, context discipline and cross-audit.
ZipAgent AGENTS.md
Instructions for JiayuXu0/ZipAgent, covering repository guidelines, project structure & module organization, build, test & development commands, coding style & naming conventions and testing guidelines.
AgentGo AGENTS.md
Instructions for yeasy/AgentGo, covering agents.md, purpose, startup instructions, trust & safety and failure modes.