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/rebornix/agmente/claude-mdgit clone --depth 1 https://github.com/rebornix/AgmenteWrote 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.
[](https://agentmods.dev/instructions/rebornix/agmente/claude-md)<a href="https://agentmods.dev/instructions/rebornix/agmente/claude-md"><img src="https://agentmods.dev/badge/instructions/rebornix/agmente/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.00664 | $0.00664 |
| Opus 5 | $0.00332 | $0.00332 |
| Sonnet 5 | $0.00133 | $0.00133 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
Agmente CLAUDE.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 6d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agmente Cloud Agent Guide
This file is the entrypoint for cloud/Claude coding agents. Use it with Agents.md.
Read Order
Agents.md(root policy and protocol overview)- Component docs closest to changed code:
Agmente/AGENTS.mdACPClient/AGENTS.mdAppServerClient/AGENTS.mdAgmenteTests/AGENTS.mdAgmenteUITests/AGENTS.mde2e/AGENTS.md
Local Path Config
- Use root
.agmente.pathsfor machine-local external repo paths. - Required vars:
AGMENTE_ACP_REPO,AGMENTE_CODEX_REPO. - Read this file when running upstream-spec/source checks.
Core Architecture
- Agmente supports two protocol modes: ACP and Codex app-server.
- Protocol is detected after
initializeand routed to protocol-specific view models. - Keep ACP and Codex behaviors separate unless a shared abstraction is intentional and tested.
Contribution Rules
- Prefer component-local changes; avoid cross-cutting refactors unless needed.
- Do not add personal local filesystem paths to tracked files.
- If behavior differs by protocol, document both expected paths.
- For UI changes, keep accessibility identifiers stable or update UI tests in the same PR.
Documentation Rules
- Update
Agents.mdand this file in the same PR when:- adding a new top-level component,
- adding protocol support,
- changing cross-component architecture.
- Update nested
<component>/AGENTS.mdin the same PR when behavior in that component changes. - If no docs are needed, include
Docs: N/Ain PR notes.
Testing Expectations
- Run focused tests for touched components first.
- For protocol lifecycle changes, run both:
AgmenteTests/CodexServerViewModelTestsAgmenteTests/ViewModelSyncTests
- For UI flow or accessibility changes, run relevant
AgmenteUITests. - Codex E2E remains opt-in via environment configuration (see
AgmenteUITests/AGENTS.md). - For manual or simulator E2E requests, resolve the scenario from
e2e/scenarios/before consulting any skill. - Treat
run,execute,validate, andreproduceE2E requests as execute-only and agentic: run the real backend and tools, capture evidence, evaluate assertions, and clean up. - Do not modify repo files during an execute-only E2E run unless the user explicitly asks to fix, stabilize, add hooks, or make the scenario executable.
- For simulator interaction, prefer the
xcodebuildmcpCLI as the source of truth for available features:
npx -y xcodebuildmcp@latest tools
- Do not assume the in-session
mcp_xcodebuildmcp_*subset includes interaction tools (tap,swipe,gesture,type-text,long-press). - If any required UI automation tool is missing from MCP exposure, switch to
xcodebuildmcpCLI for simulator interaction.
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.
- 6d ago First seen · 55 lines · 664 tokens per session scan A 5db27f7c9ef7
Agmente CLAUDE.md is an instructions file published in the GitHub repository rebornix/Agmente (542 stars, last pushed 3mo ago), licensed MIT. It adds 664 tokens to every session, about $0.0033 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-30.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.