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/ymm-oss/fsl/agents-mdgit clone --depth 1 https://github.com/ymm-oss/fslWhat 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.03287 | $0.03287 |
| Opus 5 | $0.01643 | $0.01643 |
| Sonnet 5 | $0.00657 | $0.00657 |
| Haiku 4.5 | $0.00329 | $0.00329 |
Grade A, and why
fsl 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project and authority
fslc is the verifier for FSL, an AI-native formal specification language. The native Rust
workspace under rust/ is the authoritative implementation and distribution surface, including
the fslc-lsp language server. The Python package under src/fslc/ is a frozen compatibility
reference; do not add product behavior there unless a compatibility change explicitly requires it.
Interpret evidence in this order:
- Language and CLI contracts in
docs/LANGUAGE.md, accepteddocs/DESIGN-*.md, tests, and CI. - The native Rust implementation and its public Kernel/JSON contracts.
- Observable behavior of the frozen Python reference where a parity contract applies.
- Proposals, task notes, conversation history, and agent memory.
When sources disagree, stop and resolve the contract conflict instead of silently choosing one.
Project structure
rust/fsl-syntax: lexer, parsers, source locations, and surface AST.rust/fsl-core: typed kernel model, validation, resolution, and dialect lowering.rust/fsl-runtime: solver-independent Monitor and explicit-state/BFS behavior.rust/fsl-solver*: backend-neutral solver boundary plus native and browser Z3 backends.rust/fsl-verifier: BMC, induction, refinement, liveness, and scenarios.rust/fsl-tools: analysis, mutation, report, typestate, and test generation tools.rust/fslc: native CLI and JSON/process contract.rust/fsl-wasm: browser Worker surface.rust/fsl-lsp: native language server and document index.src/fslc: frozen Python compatibility reference.tests: Python-driven Rust contract, parity, and compatibility tests.specsandexamples: FSL corpus and reproducing cases.skills: canonical agent skills;.claude/skills/fsl*and.agents/skills/fsl*symlink here.
Build and verification commands
Run the native CLI from the working tree:
cargo run --manifest-path rust/Cargo.toml -p fslc-rust --bin fslc -- check specs/cart_v1.fsl
cargo run --manifest-path rust/Cargo.toml -p fslc-rust --bin fslc -- verify specs/cart_v1.fsl --depth 8
cargo run --manifest-path rust/Cargo.toml -p fslc-rust --bin fslc -- verify specs/cart_v1.fsl --engine induction
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 · 211 lines · 3,287 tokens per session scan A 032d485ce147
fsl AGENTS.md is an instructions file published in the GitHub repository ymm-oss/fsl (21 stars, last pushed 4d ago), licensed Apache-2.0. It adds 3,287 tokens to every session, about $0.0164 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
deepagents AGENTS.md
AGENTS.md instructions for langchain-ai/deepagents, covering global development guidelines for the deep agents monorepo, corridor security analysis, development workflow, suppressing ruff rules and pr conventions.
autoharness AGENTS.md
Instructions for tigerless-labs/autoharness: This repo uses Open Knowledge — collaborative markdown via MCP. .open-knowledge/config.yml (with optional /.open-knowledge/config.yml; CLI/env may override) is the path contract: content.dir is the root for relative paths; content.include lists globs that add markdown…
cookiecutter-mlops-package AGENTS.md
Instructions for fmind/cookiecutter-mlops-package, covering agents.md, project overview, setup & core commands, definition of done and conventions & idioms.
python-cheatsheet copilot-instructions.md
Copilot instructions for labex-labs/python-cheatsheet, covering python cheatsheet - ai coding assistant instructions, project overview, architecture & key patterns, content structure and routing & layout system.
martex-quant CLAUDE.md
Instructions for martex-dev/martex-quant, covering session start — read these first, project instructions, ai trading bot project - master instructions, role and project objective.
ZipAgent AGENTS.md
Instructions for JiayuXu0/ZipAgent, covering repository guidelines, project structure & module organization, build, test & development commands, coding style & naming conventions and testing guidelines.