Hexis: Instructions file for Codex

AGENTS.md

Hexis AGENTS.md is an instructions file for Codex, OpenCode from Bevel-Software/Hexis. It costs 468 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for coding agents working on the Hexis project. They explain which agent-facing guides and tests must change when tools, arguments, paths, permissions, or other observable behaviour changes.

In plain words
What is it for?
They are for maintaining agent guides, handshake instructions, tool descriptions, snapshots, and related tests while changing the repository.
Why use it?
They help keep the instructions given to coding agents consistent with the software they describe. Without this, agents may follow outdated guidance or tests may fail because the documented tool surface is stale.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Claude Code; mentions Codex.

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/bevel-software/hexis/agents-md"><img src="https://agentmods.dev/badge/instructions/bevel-software/hexis/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 468 This file is loaded in full into every session.
When invoked 468 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.00468 $0.00468
Opus 5.5 $0.00187 $0.00187
Sonnet 5.5 $0.00094 $0.00094
Haiku 4.5 $0.00047 $0.00047

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

Security

Grade A, and why

Hexis 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 8d 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 · 36 lines

What it actually says

Working in this repository

For coding agents (Claude Code, Codex, Cursor and others) and the people who run them.

Change behaviour, update the agent guide in the same pull request

The platform tells every connected agent how it works: the guide in packages/core-backend/agent-guide/ (served by get_agent_guide), the handshake instructions in packages/core-backend/src/modules/agent-instructions/, and each tool's description and arguments. When you change something an agent can observe (a tool, an argument, a refusal, a path, an access rule, what a draft or a change request does), update that text in the same pull request.

  • packages/core-backend/src/modules/agent-guide/__tests__/ holds the text to the code: every tool, argument, path and section the guide names, the token budgets in guide-budget.ts, the ten evaluation tasks, and a snapshot of the tool surface (tool-surface.json).
  • A change to the tools or their arguments fails the snapshot. Update the guide if agents need to know, then accept the new surface: pnpm --filter @bevel-software/platform-core-backend exec vitest run src/modules/agent-guide -u. If no guide change is needed, say so in the pull request description.
  • Before you add guidance, apply the scoring rule in openspec/changes/agent-guide-layers/design.md: is there evidence an agent gets it wrong; can it learn it from the tool's description or error instead; is it true for every deployment; what does it cost; is it already said? Say each thing once.
  • A section that needs more room raises its budget in guide-budget.ts, with the reason in the pull request.
  • Bevel's team: before changing any of this text, run the agent-guide benchmark (private, in bevel-platform at evals/agent-guide/) with the change against its base, and say in the pull request what it found.

Prose in the guide follows the house style: plain, short sentences, no em dashes.

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. 8d ago First seen · 36 lines · 468 tokens per session scan A b0320e460c66

Subscribe to this mod's changes

Hexis AGENTS.md is an instructions file published in the GitHub repository Bevel-Software/Hexis (123 stars, last pushed yesterday), licensed Apache-2.0. It adds 468 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-10-30.

Related

Hexis AGENTS.md compared with instructions from other repositories

Hexis AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
Hexis AGENTS.mdBevel-Software/HexisInstructions file123yesterdayApache-2.0A468Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode