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/myrialabs/clopen/agents-mdgit clone --depth 1 https://github.com/myrialabs/clopenWhat 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.00697 | $0.00697 |
| Opus 5 | $0.00349 | $0.00349 |
| Sonnet 5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
clopen 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Guidelines for Clopen
This document provides guidelines for AI coding agents when working on the Clopen project.
WORK PROTOCOL
Before Coding
- Identify which stage is currently being worked on
- Understand the specific task that needs to be completed
- For PR-related tasks (e.g., "review PR #123", "check PR X"), read
MAINTAINERS.mdfirst to understand the PR workflow, review process, and maintainer conventions
During Coding
- Follow agreed-upon architecture and patterns
- Do not change technical decisions without discussion
- Ensure code matches the established folder structure
- Use chosen libraries and frameworks
- Do NOT run
bun run devorbun run buildcommands
After Coding
- Run
bun run checkandbun run lintto ensure code functions properly - Do not create any .md files unless explicitly instructed
- Suggest a branch name and commit message following CONTRIBUTING.md conventions:
- Branch:
<type>/<description>— lowercase, kebab-case, concise - Commit:
<type>(<scope>): <subject>— imperative mood, lowercase, no period, max 72 chars - Do NOT create the branch or commit automatically — only suggest the names for review
- Branch:
IMPORTANT RULES
- Be CONSISTENT with previously made decisions
- COMMUNICATE if existing plans need to be changed
- STOP after each stage for review
PROJECT-SPECIFIC GUIDELINES
Runtime & Package Manager
- Bun-only project — Node.js and Deno are NOT supported
- Always use
buncommands (never npm/pnpm/yarn) - Runtime checks exist in
bin/clopen.tsandbackend/index.ts
Architecture
- Backend: Bun + Elysia with WebSocket architecture
- Frontend: Svelte 5 with runes system ($state, $derived, $effect)
- Database: SQLite with migration system
Code Style
- TypeScript throughout the entire codebase
- Use
constby default; useletonly when reassignment is needed - In
.sveltefiles:letfor$stateand$bindable;constfor$derived,$props, functions - Use Svelte 5 runes for state management (not traditional stores)
- Follow Tailwind CSS v4 conventions
- Use custom logger module (
debug) instead of console.*
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 · 97 lines · 697 tokens per session scan A 36729e5bfcdb
clopen AGENTS.md is an instructions file published in the GitHub repository myrialabs/clopen (40 stars, last pushed 4d ago), licensed MIT. It adds 697 tokens to every session, about $0.0035 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
DevoxxGenieIDEAPlugin GEMINI.md
Instructions for devoxx/DevoxxGenieIDEAPlugin, a project described as: DevoxxGenie is an agentic plugin for IntelliJ IDEA that uses local LLM's (Ollama, LMStudio, GPT4All, Jan and Llama.cpp) and Cloud based LLMs to help review, test, explain your project code. Latest version now also supports Spec Driven Development…
packmind packmind-frontend-error-management.instructions.md
Instructions for PackmindHub/packmind: A global error boundary is already configured at the root level (in root.tsx) that automatically catches all page crashes, 404s, and loader failures. This standard defines when and how to use explicit... .
Ctxo CLAUDE.md
Instructions for alperhankendi/Ctxo, covering claude.md — ctxo, project overview, quick reference, dev (pnpm workspace) and usage (consumer).
apex-accelerator no-interactive-shell.instructions.md
Prevents interactive shell prompts and long-output terminal replays from being injected into chat. Forbids -i flags on mv/rm/cp, read -p, and confirm prompts (incl. inside bash -c '...'). Pipe long output to files. Scoped to chat-context-loaded files; skill references/ and templates/ are exempt because they hold…
apex-accelerator iac-bicep-best-practices.instructions.md
Bicep-specific IaC best practices for Azure templates. Security baseline, naming, AVM mandate, anti-patterns.
llm-ide-rules pytest-integration-tests.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering pytest integration tests and example integration test.