agentmods.dev

clude: Instructions file for Codex

AGENTS.md

clude AGENTS.md is an instructions file for Codex, OpenCode from sebbsssss/clude. It costs 486 tokens per session, scanned A, original, MIT.

Repository instructions for Clude, a bot, including its related gstack workflow tools and a required memory system. They define how agents should recall and save project information and how work moves through staging.

In plain words
What is it for?
Using the listed workflow commands, recalling relevant project memories, recording decisions and findings, and following the required staging process.
Why use it?
They preserve useful context between conversations and set shared rules for browsing, planning, reviewing, testing, and releasing work.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md; mentions Codex; built for gstack.

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

not rated 22repo 1mo ago A scan 486 tokens original MIT
View source ↗ sebbsssss/clude cluude.vercel.app
Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/sebbsssss/clude/agents-md"><img src="https://agentmods.dev/badge/instructions/sebbsssss/clude/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 486 This file is loaded in full into every session.
When invoked 486 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.00486 $0.00486
Opus 5.5 $0.00194 $0.00194
Sonnet 5.5 $0.00097 $0.00097
Haiku 4.5 $0.00049 $0.00049

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

Security

Grade A, and why

clude 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 · 35 lines

What it actually says

Clude Bot

gstack

Use the /browse skill from gstack for all web browsing. Never use mcp__claude-in-chrome__* tools.

Available skills: /office-hours, /plan-ceo-review, /plan-eng-review, /plan-design-review, /design-consultation, /review, /ship, /browse, /qa, /qa-only, /design-review, /setup-browser-cookies, /retro, /investigate, /document-release, /codex, /careful, /freeze, /guard, /unfreeze, /gstack-upgrade.

Clude Memory (Required for ALL agents)

Clude is our product. Every agent MUST actively use it. The clude-memory MCP server is configured in .mcp.json.

Every heartbeat / conversation, you MUST:

  1. Store memories about your work: decisions made, findings, blockers, task outcomes, things learned. Use store_memory with source: "mcp:<your-role>" (e.g. mcp:ceo, mcp:lead-pm, mcp:researcher).
  2. Recall memories when starting work on a topic you may have context on. Use recall_memories before diving in.
  3. Minimum 1 memory per heartbeat where you do meaningful work. More is better.

Memory type guide:

  • episodic — events, task completions, meetings, incidents
  • semantic — facts, knowledge, architecture decisions, team info
  • procedural — how-to knowledge, workflows, patterns that work
  • self_model — reflections on your own performance, strengths, gaps

Always include: meaningful tags, importance (0-1), and summary. This is our product — dogfood it seriously.

Staging Workflow (Required)

All changes go through staging first. See CLAUDE.md for the full workflow.

Key rules for all agents:

  • All PRs target staging, never main
  • No direct pushes to main or staging
  • Board verifies at cludebot-test-preview.up.railway.app before approving merge to main
  • When shipping, always set base branch to staging
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. 2mo ago First seen · 35 lines · 486 tokens per session scan A fbffed7ff204

Subscribe to this mod's changes

clude AGENTS.md is an instructions file published in the GitHub repository sebbsssss/clude (22 stars, last pushed 1mo ago), licensed MIT. It adds 486 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-08-30.

Related

clude AGENTS.md compared with instructions from other repositories

clude AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
clude AGENTS.mdsebbsssss/cludeInstructions file221mo agoMITA486Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,516GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA2,022GitHub Copilot