Borrowing it
Nothing to install: this file belongs to MLXPorts/xLSTM-metal. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MLXPorts/xLSTM-metal/main/AGENTS.mdgit clone --depth 1 https://github.com/MLXPorts/xLSTM-metalWrote 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/mlxports/xlstm-metal/agents-md)<a href="https://agentmods.dev/instructions/mlxports/xlstm-metal/agents-md"><img src="https://agentmods.dev/badge/instructions/mlxports/xlstm-metal/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.
<a href="https://agentmods.dev/instructions/mlxports/xlstm-metal/agents-md"><img src="https://agentmods.dev/badge/instructions/mlxports/xlstm-metal/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.01075 | $0.01075 |
| Opus 5 | $0.00537 | $0.00537 |
| Sonnet 5 | $0.00215 | $0.00215 |
| Haiku 4.5 | $0.00108 | $0.00108 |
Grade A, and why
xLSTM-metal 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 10d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent and Developer Guide
This repo implements xLSTM for Apple Silicon using MLX with Metal Accelerated Dispatch (MAD). These guidelines ensure production-safe development.
Quick Reference
Primary Entry Point: generate.py - Production runner using MLX backend
Core Implementation: xlstm_metal/ - MAD wiring, blocks, and inference
Tests: run_pytest.py - Test suite runner
Documentation: docs/ - Technical documentation by component
CLAUDE Guidance (Read Me First)
This repo runs on Apple Silicon with MLX-first compiled backends. These rules are strict so your help stays production-safe and useful.
Zero-Mock Policy (Production Code)
- Don’t add mocks, stubs, or fake implementations to production paths. Use real implementations or leave TODOs in comments with precise next steps.
- If a mock is unavoidable for a demo, place it under test or example folders only, guarded by clear naming and comments. Never wire a mock into default execution.
Always Reuse Before Rebuilding
- Before implementing anything, search the repo for existing code:
rg -n "symbol|filename|keyword"to locate reuse targets.- Scan
xlstm_metal/,scripts/, anddocs/for prior art and conventions.
- Prefer refactoring or adapting existing modules to new needs rather than new, parallel implementations.
- If you must introduce new code, explain why reuse was insufficient and reference your searches.
Lead With Vulnerability
- Be explicit about what you don’t know or what isn’t working yet.
- State assumptions and risks up front. Offer a short plan with checkpoints.
- After changes, verify and report limits (“what this didn’t solve”).
Respect the Shell and Filesystem
- Use OS tools for file ops; avoid dumping large files into the terminal:
- Copy/rename:
cp,mv(not read‑and‑reprint). - Search:
rg(ripgrep) for speed and focus. - Inspect selectively:
sed -n '1,200p' <file>(chunked views only).
- Copy/rename:
- Don’t stream giant artifacts or model weights to stdout. If you need to show something, quote only the relevant lines.
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.
- 10d ago First seen · 107 lines · 1,075 tokens per session scan A b6b6ed2d9cf5
xLSTM-metal AGENTS.md is an instructions file published in the GitHub repository MLXPorts/xLSTM-metal (11 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 1,075 tokens to every session, about $0.0054 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.