agentleFS
zedarvateszedarvates/botte-secrete/AGENTS.md

botte-secrete

AGENTS.md2 starsChanged 3 months agoMITView on GitHub

Guidance for AI agents (Claude Code, Codex, Cursor, Copilot, …) working in this repo. Companion to the README. Kept short on purpose — see linked docs for detail. A multi-agent token-optimization toolkit: code audit, automated fixes, per-project skill filtering, local-LLM routing, and adversarial red-teaming — built to lean on local hardware and cheap models wherever possible. - Language: Python 3.10+, standard library only (no runtime dependencies for the core modules). On Windows use python (not python3, which may be a…

The file

We split this AGENTS.md into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run a module: python -m skills.<module>.cli ...

    line 17
  2. Very specific:

    Compact output: Prefer the JSON schemas in docs/schemas/ over verbose markdown for inter-agent reports.

    line 34
  3. Very specific:

    Run the relevant tests, keep diffs minimal, and don't commit machine-specific generated files (e.g.

    line 47
  4. Distinctive:

    Batch independent tool calls: read multiple files, search multiple patterns, extract multiple URLs in ONE turn instead of chaining them …

    line 54
  5. Very specific:

    Cache checkup/bench results: if you ran checkup . or bench less than 5 min ago with no file changes since, use the cached result from …

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

AGENTS.md — Botte Secrète

Guidance for AI agents (Claude Code, Codex, Cursor, Copilot, …) working in this repo. Companion to the README. Kept short on purpose — see linked docs for detail.

What this is

A multi-agent token-optimization toolkit: code audit, automated fixes, per-project skill filtering, local-LLM routing, and adversarial red-teaming — built to lean on local hardware and cheap models wherever possible.

Setup & commands

  • Language: Python 3.10+, standard library only (no runtime dependencies for the core modules). On Windows use python (not python3, which may be a stub).
  • Run a module: python -m skills.<module>.cli ...
  • Tests (214+ passing, 77 new Fable6 tests via pytest):
    • Full pipeline: python skills/test_e2e.py
    • Fable6 skills: python -m pytest --rootdir=. -q
    • Module tests: python -m skills.<module>.test_<module> for llm_backends, directives_audit, auto_router, skill_finder, bootstrap, infra_advisor.
  • Pre-commit checks: python scripts/pre-commit-check.py --fast

Conventions (non-negotiable)

  • Stdlib-first. Reach for a dependency only when the stdlib genuinely can't do it. The "laziness ladder": does it need to exist? → stdlib → native feature → existing dep → one line → minimum that works. Never cut input validation, error handling, security, or accessibility.
  • Always pass encoding="utf-8" to open / read_text / write_text, and call skills.console_utf8.force_utf8() in scripts that print emoji — Windows consoles default to cp1252 and crash otherwise.
  • Compact output. Prefer the JSON schemas in docs/schemas/ over verbose markdown for inter-agent reports; group findings by file; truncate long lists.
  • Token budgets per agent are enforced (see README "Token Budgets").
  • Match the surrounding file's style; keep architecture flat.

Layout

  • skills/ — one folder per capability, each with a SKILL.md.
  • scripts/ — standalone tools and hooks.
  • docs/plans/ — design docs; docs/schemas/ — report schemas.

Before you finish

Run the relevant tests, keep diffs minimal, and don't commit machine-specific generated files (e.g. configs/llm-endpoints.json, .mcp.json — both ignored).

Botte Secrète policy

This project follows .botte/policy.md (prefer local models for cheap work, improve prompts locally, run /checkup after updates). Read it.

Token-efficient workflows

  • Batch independent tool calls: read multiple files, search multiple patterns, extract multiple URLs in ONE turn instead of chaining them sequentially. Each round-trip costs context tokens.
  • Never re-read after edit: the edit tool guarantees the post-edit state. Only re-read a file when you need it for a DIFFERENT purpose.
  • Cache checkup/bench results: if you ran checkup . or bench less than 5 min ago with no file changes since, use the cached result from .botte-cache/ instead of re-scanning.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.