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/coollabsio/jean/agents-mdgit clone --depth 1 https://github.com/coollabsio/jeanWrote 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/coollabsio/jean/agents-md)<a href="https://agentmods.dev/instructions/coollabsio/jean/agents-md"><img src="https://agentmods.dev/badge/instructions/coollabsio/jean/agents-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 | $0.07237 | $0.07237 |
| Opus 5 | $0.03619 | $0.03619 |
| Sonnet 5 | $0.01447 | $0.01447 |
| Haiku 4.5 | $0.00724 | $0.00724 |
Grade A, and why
jean 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 4d 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 — 568 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agents
Current Status
@CLAUDE.local.md
Overview
This repository is a template with sensible defaults for building Tauri React apps.
Core Rules
Codex App Server schema
If you need to check some codex app-server related things, use "codex app-server generate-json-schema --out ./codex-schema" to generate schema and check local dir ./codex-schema for schemas.
New Sessions
- Read @docs/tasks.md for task management
- Review
docs/developer/architecture-guide.mdfor high-level patterns - Check
docs/developer/for system-specific patterns (command-system.md, performance-patterns.md, etc.) - Check git status and project structure
Development Practices
CRITICAL: Follow these strictly:
- Read Before Editing: Always read files first to understand context
- Follow Established Patterns: Use patterns from this file and
docs/developer - Senior Architect Mindset: Consider performance, maintainability, testability
- Batch Operations: Use multiple tool calls in single responses
- Match Code Style: Follow existing formatting and patterns
- Test Coverage: Write comprehensive tests for business logic
- Quality Gates: Run
bun run check:allafter significant changes - Dev Server: You may start the dev server (
bun run tauri dev) when needed - No Unsolicited Commits: Only when explicitly requested
- Documentation: Update relevant
docs/developer/files for new patterns - Removing files: Always use
rm -f
CRITICAL: Use Tauri v2 docs only. Always use modern Rust formatting: format!("{variable}")
Architecture Patterns (CRITICAL)
State Management Onion
useState (component) → Zustand (global UI) → TanStack Query (persistent data)
Decision: Is data needed across components? → Does it persist between sessions?
Performance Pattern (CRITICAL)
// ✅ GOOD: Use getState() to avoid render cascades
const handleAction = useCallback(() => {
const { data, setData } = useStore.getState()
setData(newData)
}, []) // Empty deps = stable
// ❌ BAD: Store subscriptions cause cascades
const { data, setData } = useStore()
const handleAction = useCallback(() => {
setData(newData)
}, [data, setData]) // Re-creates constantly
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.
- 4d ago First seen · 568 lines · 7,237 tokens per session scan A 14c1638c70cc
jean AGENTS.md is an instructions file published in the GitHub repository coollabsio/jean (1,250 stars, last pushed 9d ago), licensed Apache-2.0. It adds 7,237 tokens to every session, about $0.0362 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
kosho CLAUDE.md
Instructions for carlsverre/kosho, covering claude.md, current development, build & test commands, code style guidelines and testing guidelines.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
InvestSkill GEMINI.md
Gemini CLI instructions for yennanliu/InvestSkill, covering investskill — gemini cli setup & usage guide, installation & setup, quick start, navigate to the investskill directory and start gemini cli (loads gemini.md automatically).
she-love-me CLAUDE.md
Instructions for 863401402/she-love-me, covering claude.md and 唯一工作流.
SeekMoney-ai CLAUDE.md
Instructions for zykooooooooo/SeekMoney-ai, covering claude.md, project overview, development commands, development and production.
slivingdoc AGENTS.md
AGENTS.md instructions for baalimago/slivingdoc, covering agents.md — slivingdoc, architecture, package map, event flow and startup wiring (main.go).