Borrowing it
Nothing to install: this file belongs to LeandroPG19/Memorys. 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/LeandroPG19/Memorys/main/AGENTS.mdgit clone --depth 1 https://github.com/LeandroPG19/MemorysWrote 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/leandropg19/memorys/agents-md)<a href="https://agentmods.dev/instructions/leandropg19/memorys/agents-md"><img src="https://agentmods.dev/badge/instructions/leandropg19/memorys/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/leandropg19/memorys/agents-md"><img src="https://agentmods.dev/badge/instructions/leandropg19/memorys/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.01390 | $0.01390 |
| Opus 5.5 | $0.00556 | $0.00556 |
| Sonnet 5.5 | $0.00278 | $0.00278 |
| Haiku 4.5 | $0.00139 | $0.00139 |
Grade A, and why
Memorys 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 21d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent contract — MemoryIndustry
Claude Code / Cursor / CLI: if a global rule (rust.mdc, «cero comentarios», plant e2e) clashes with this file, this repo wins.
Mergeable (local CI only)
Mergeable means ./scripts/merge-gate.sh exited 0 in this turn with a clean log: no SKIPPED, no soft alerts, no “should pass”.
Aliases of the same SIL: ./scripts/como-el-ci.sh todo, ./scripts/como-el-ci.sh extra, ./scripts/memory-industry-test.sh all.
GitHub Actions is not the merge judge. A green badge is not mergeable. That workflow excludes MODEL_OR_CLI_ONLY and has no ONNX / NLI / reranker / generative LLM. ci.yml runs only when dispatched by hand.
Publishing is ./scripts/release.sh vX.Y.Z and nothing else. When merge-gate.sh already passed on that exact commit over a clean tree, it left ~/.cache/cuba-gate/receipts/<sha> and release.sh tags from that receipt without running the gate a second time; otherwise, or with --rerun-gate, it runs merge-gate.sh on origin/main. Either way it pushes an annotated tag carrying local-gate: MERGE GATE PASSED <sha> only on a clean exit 0. publish.yml reads that line and asks GitHub's CI nothing.
Two judges, chained
| Judge | What it is | What it is not |
|---|---|---|
./scripts/merge-gate.sh |
The SIL. fmt, clippy -D warnings, --ignored, e2e (no soft-skip), deny, audit, codigo-muerto, crap-gate floor, mutants-gate on mmr/rrf/cache. |
A fraction (cargo test --lib). GitHub Actions. |
./scripts/quality-gate.sh |
CRAP/lizard + cargo mutants on rust/src in the diff. |
A substitute for the SIL. Does not run merge-gate. |
quality-gate after the SIL when the change touched rust/src or Python. A missing lizard / cargo-mutants is exit 2: the hardener does not close.
Six-pack
Behaviour change: especificador → implementador → mejorador → arquitecto → endurecedor → qa.
Handoffs: .cursor/handoffs/*.yml. Judge: ./scripts/validar-handoff.sh. Example: .cursor/handoffs/handoff.example.yml.
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.
- 21d ago Changed · +1 lines · +254 tokens per session 3390fa38eacd
- 1mo ago Changed · +31 lines · +734 tokens per session 8aa47b86f52c
- 1mo ago First seen · 44 lines · 402 tokens per session scan A 15350c3314a7
Memorys AGENTS.md is an instructions file published in the GitHub repository LeandroPG19/Memorys (30 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,390 tokens to every session, about $0.0056 per session on Opus 5.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-09-12.
Other instructions, from other repositories
vibetags com-example-service-NewAnnotationsShowcase-SandboxTestHelper.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for sandboxtesthelper and sandbox restriction.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).