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/triplesixmir/reporecall/agents-mdgit clone --depth 1 https://github.com/triplesixmir/reporecallWhat 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.00092 | $0.00092 |
| Opus 5 | $0.00046 | $0.00046 |
| Sonnet 5 | $0.00018 | $0.00018 |
| Haiku 4.5 | $0.00009 | $0.00009 |
Grade A, and why
reporecall 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 yesterday.
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.
What it actually says
RepoRecall memory
Canonical memory files are Markdown with YAML frontmatter and are the durable source of truth. SQLite is only a rebuildable local index. Do not store secrets, credentials, private keys, or raw transcripts in memory files.
Use RepoRecall MCP tools or the local CLI for memory operations. Durable session summaries are created only after an explicit checkpoint.
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.
- yesterday First seen · 8 lines · 92 tokens per session scan A fbc8e412ce81
reporecall AGENTS.md is an instructions file published in the GitHub repository triplesixmir/reporecall (0 stars, last pushed 10d ago), licensed MIT. It adds 92 tokens to every session, about $0.0005 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-31.
Other instructions, from other repositories
anarlog AGENTS.md
AGENTS.md instructions for fastrepl/anarlog, covering commands, pre-commit verification, guidelines, code style and cli tui command architecture.
personal-model AGENTS.md
Instructions for Intuition-Lab/personal-model, covering agents.md, runtime boundary, commands, pipeline and documentation map.
plur CLAUDE.md
Instructions for plur-ai/plur, covering claude.md, what is plur, development, package dependency and version bumps.
personal-model CLAUDE.md
Instructions for Intuition-Lab/personal-model: Read and follow AGENTS.md. It is the single agent orientation for this repository: Runtime boundary, commands, architecture, invariants, current documentation, privacy rules, and DCO workflow.
engraphis AGENTS.md
Instructions for Coding-Dev-Tools/engraphis, covering agents.md — engraphis, 0. read this first — two architectures live in one package, 1. commands, ── unified dashboard + memory inspector ── and 2. the v2 recall pipeline (where the real work is).
paxm AGENTS.md
Instructions for pax-beehive/paxm, covering paxm 开发要求, git 与协作, 架构边界, 代码与验证 and 文档与发布.