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/tadmstr/backrest-mcp/agents-mdgit clone --depth 1 https://github.com/TadMSTR/backrest-mcpWrote 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/tadmstr/backrest-mcp/agents-md)<a href="https://agentmods.dev/instructions/tadmstr/backrest-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/tadmstr/backrest-mcp/agents-md.svg" alt="Measured on agentmods" 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 | $0.01660 | $0.01660 |
| Opus 5 | $0.00830 | $0.00830 |
| Sonnet 5 | $0.00332 | $0.00332 |
| Haiku 4.5 | $0.00166 | $0.00166 |
Grade A, and why
backrest-mcp 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 3d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
backrest-mcp
Python/FastMCP MCP server (stdio or loopback HTTP transport) wrapping the Backrest backup
manager REST API. Field names target the deployed Backrest v1.13.0 connect-rpc API
(upstream main has since diverged — see CHANGELOG.md 0.3.0).
What it does
Provides MCP tools for querying backup operations, listing snapshots, reading config, browsing snapshot contents, triggering backups, running repo maintenance tasks, and (with explicit opt-in) forgetting snapshots and restoring data to staging paths.
Tools
Always registered (read-only):
get_health()— Reachability + credential health (ok/auth_failed/unreachable); poll-safeget_config()— Read Backrest configuration (repos, plans, global settings)list_snapshots(repo_id?, plan_id?)— List snapshots; no args → enumerate all repos, tag eachlist_snapshot_files(repo_id, snapshot_id, path?)— Browse files (repo_id resolved to GUID internally)get_summary()— 30-day dashboard stats per repo and planget_operations(plan_id?, repo_id?, limit?)— Recent operations with status icons + log refsget_logs(ref, max_bytes?)— Read an operation's log (ref surfaced byget_operations; Connect stream)get_download_url(operation_id, file_path)— Signed URL for a restored file
Registered when BACKREST_READONLY=false:
trigger_backup(plan_id, dry_run?)— Trigger a backup plando_repo_task(repo_id, task)— Run maintenance: index/prune/check/stats/unlock/forgetcancel_operation(operation_id)— Cancel a running operation
Registered when BACKREST_ALLOW_DESTRUCTIVE=true (requires READONLY=false):
forget_snapshot(snapshot_id, repo_id, confirm, plan_id?)— Permanently forget a snapshotrestore_snapshot(snapshot_id, repo_id, path, target, plan_id?)— Restore to staging path
Intentionally NOT exposed (dangerous — keep unregistered): RunCommand (arbitrary
restic execution), SetConfig, AddRepo, RemoveRepo (deletes history), ClearHistory.
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.
- 3d ago First seen · 125 lines · 1,660 tokens per session scan A 75d5ed3b4e27
backrest-mcp AGENTS.md is an instructions file published in the GitHub repository TadMSTR/backrest-mcp (0 stars, last pushed 4d ago), licensed MIT. It adds 1,660 tokens to every session, about $0.0083 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
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.
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.
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 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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.