Borrowing it
Nothing to install: this file belongs to Alfredvc/rema1000-cli. 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/Alfredvc/rema1000-cli/main/AGENTS.mdgit clone --depth 1 https://github.com/Alfredvc/rema1000-cliWrote 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/alfredvc/rema1000-cli/agents-md)<a href="https://agentmods.dev/instructions/alfredvc/rema1000-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/alfredvc/rema1000-cli/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/alfredvc/rema1000-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/alfredvc/rema1000-cli/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.00712 | $0.00712 |
| Opus 5.5 | $0.00285 | $0.00285 |
| Sonnet 5.5 | $0.00142 | $0.00142 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
rema1000-cli 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 1mo 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
REMA 1000 CLI — Agent Reference
Quick Start
# Authenticate (one-time, requires browser)
rema auth login
# Verify auth
rema auth status
Commands
All commands output JSON to stdout. Errors go to stderr as {"error": "..."}.
Global Flags
--json— compact JSON (overrides TTY pretty-printing)--fields f1,f2— return only these fields (reduces tokens)
Authentication
| Command | Description |
|---|---|
rema auth login |
Browser-based phone auth |
rema auth status |
Auth state and token expiry |
rema auth logout |
Delete tokens |
Read Commands (GET)
| Command | Auth | Description |
|---|---|---|
rema version |
No | App version and maintenance status |
rema customer get |
Yes | Full customer profile |
rema customer minimal |
Yes | Bonus balance + primary store |
rema offers list |
Yes | Offers, missions, price cuts |
rema campaigns list [--type SP] |
Yes | Sales campaigns with products |
rema articles search <query> [--rows N] |
Yes | Product search |
rema articles image <gtin> [--output file] |
Yes | Product image (binary) |
rema stores get <workplace-id> |
Yes | Store details |
rema stores search <query> |
Yes | Search stores |
rema stores hours <store-number> |
Yes | Weekly opening hours |
rema transactions list |
Yes | Transaction history headers |
rema transactions get <transaction-id> |
Yes | Line items + payments for one transaction |
rema lists list |
Yes | All shopping lists |
rema lists get <list-id> |
Yes | List with items |
rema lists image <list-id> [--output file] |
Yes | List custom image (binary) |
Write Commands (POST/PUT)
| Command | Description |
|---|---|
rema customer update --home-store <id> |
Set home store |
rema lists create <name> [--emoji X] [--theme COLOR] |
Create list |
rema lists delete <list-id> |
Delete list |
rema lists share <list-id> --name <name> |
Generate share link |
rema items add <list-id> <name> [--gtin X] [--description X] [--quantity N] [--store-area N] |
Add item |
rema items update <list-id> <item-id> [--state Active|Inactive] [--name X] [--quantity N] |
Update item |
rema items delete <list-id> <item-id> |
Delete item |
rema items clear <list-id> |
Remove checked-off items |
rema items activate <list-id> |
Uncheck all items |
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.
- 1mo ago First seen · 68 lines · 712 tokens per session scan A c9ef50873d0e
rema1000-cli AGENTS.md is an instructions file published in the GitHub repository Alfredvc/rema1000-cli (13 stars, last pushed 6mo ago), licensed MIT. It adds 712 tokens to every session, about $0.0028 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-08-30.
Other instructions, from other repositories
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
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).