What is agentistics AGENTS.md?

Repository process instructions for AI coding assistants, covering issues, project-board status, pull requests, merges, and documentation.

Use them when contributing code to the agentistics repository.

They make the expected development workflow explicit before implementation begins and during review and release work.

How blpsoares/agentistics configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to blpsoares/agentistics. 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/blpsoares/agentistics/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/blpsoares/agentistics

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/blpsoares/agentistics/agents-md/github.svg)](https://agentmods.dev/instructions/blpsoares/agentistics/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/blpsoares/agentistics/agents-md"><img src="https://agentmods.dev/badge/instructions/blpsoares/agentistics/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/blpsoares/agentistics/agents-md"><img src="https://agentmods.dev/badge/instructions/blpsoares/agentistics/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,346 This file is loaded in full into every session.

When invoked 1,346 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.

Model	Per session	Once invoked
Fable 5.1	$0.01346	$0.01346
Opus 5.5	$0.00538	$0.00538
Sonnet 5.5	$0.00269	$0.00269
Haiku 4.5	$0.00135	$0.00135

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

Security

Grade A, and why

agentistics 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 · 88 lines

How it starts

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

AGENTS.md — process rules for any AI coding assistant working in this repo

This file follows the agents.md convention and is read by AI coding harnesses (Claude Code, Codex CLI, Cursor, Amp, Jules, Gemini CLI, and any other tool that supports it). It defines the process every harness must follow when doing implementation work in this repo — Issues, the Project board, Discussions, and documentation. It does not duplicate architecture or implementation detail: those live in docs/ (canonical) and in each harness's own config (CLAUDE.md for Claude Code).

Before starting implementation work

Check the Project board and open Issues for an item that already covers the task. If none exists, open one — use the bug_report or feature_request issue template as fits the change.
New Issues land on the board automatically (.github/workflows/project-add.yml). Set:
- Status — Backlog on creation, In progress once work actually starts, In review once a PR is open, Done when it merges. Don't leave a card silently stale in the wrong column.
- Priority — P0 / P1 / P2. Ask the user if it's unclear; never guess P0.
Architecture-affecting or breaking changes get a Discussion first, in the Ideas category, before an Issue is opened — link the Issue back to the Discussion once it exists. Skip this step for bug fixes, docs-only changes, and scoped features that don't change a public contract (an API route, the SessionMeta shape, a CLI flag, the HarnessAdapter contract, a stored document shape, etc.). When in doubt, open the Discussion — reverting a merged breaking change is far more expensive than a skipped conversation.

Opening a PR

Link the Issue it addresses — Closes #N / Fixes #N / Resolves #N in the PR body, when one exists. This is a convention, not an enforced gate: there is deliberately no CI check and no branch protection requiring it — an Issue must never block someone from shipping a fix. Link it because it keeps the Project board accurate, not because something will reject the PR if you don't.
Follow CONTRIBUTING.md for setup, running tests, and commit conventions (Conventional Commits, English).
Fill in the PR template for real — a "Summary" with no "Motivation" or "Test plan" is not a filled template.

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

2mo ago Changed · +23 lines · +366 tokens per session 1559029b25f9
2mo ago First seen · 65 lines · 980 tokens per session scan A 03da48627251

Subscribe to this mod's changes

agentistics AGENTS.md is an instructions file published in the GitHub repository blpsoares/agentistics (44 stars, last pushed 1mo ago), licensed MIT. It adds 1,346 tokens to every session, about $0.0054 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-09-01.

Commits Git and workflow Project management Releases agents agents-skills ai llm-metrics metrics

agentistics AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
agentistics AGENTS.mdblpsoares/agentistics	Instructions file	44	1mo ago	MIT	A	1,346	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

agentistics: Instructions file for Codex