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/ishan-parihar/amazon-lyr/agents-mdgit clone --depth 1 https://github.com/ishan-parihar/amazon-lyrWrote 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/ishan-parihar/amazon-lyr/agents-md)<a href="https://agentmods.dev/instructions/ishan-parihar/amazon-lyr/agents-md"><img src="https://agentmods.dev/badge/instructions/ishan-parihar/amazon-lyr/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.1 | $0.00954 | $0.00954 |
| Opus 5 | $0.00477 | $0.00477 |
| Sonnet 5 | $0.00191 | $0.00191 |
| Haiku 4.5 | $0.00095 | $0.00095 |
Grade A, and why
amazon-lyr 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 5d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Agent Developer Guide for amazon-lyr
Project Overview
- Project: amazon-lyr — Amazon research & shopping MCP server + CLI (search, product details, reviews, cart, orders)
- Language: Python 3.11+
- Package Manager: uv
- Repository: https://github.com/ishan-parihar/amazon-lyr
- Family: part of the
-lyrseries (reddit-lyr, twitter-lyr, threads-lyr…) — browser-cookie auth, no official API keys
Build, Lint, and Test Commands
uv sync --extra dev # install deps
uv run ruff check . # lint
uv run ruff format --check . # format check
uv run pytest -q # tests (no live Amazon calls; fixtures only)
uv run amazon-lyr # CLI home view
uv run amazon-lyr serve # MCP server (stdio)
Run one test: uv run pytest tests/test_parsers.py::test_parse_search -v
Code Style
- Line length 100; ruff rules E/F/I/B/UP (see pyproject)
from __future__ import annotationsat top of all modules- snake_case functions, PascalCase classes, UPPER_SNAKE constants
- Custom exceptions in
exceptions.py, baseAmazonError(RuntimeError) - Tools wrap client calls in
try/except → handle_api_error(e)(returns NoReturn) - Read tools annotated
{"readOnlyHint": True}; destructive ones setdestructiveHint
Architecture
amazon_lyr/
├── cli_main.py # argparse entry; subcommands; TOON default output
├── cli_actions.py # command dispatch + TOON/JSON formatting
├── server.py # create_mcp_server() — FastMCP assembly
├── dependencies.py # singleton AmazonClient accessor
├── authentication.py # validate_session / get_auth_status
├── cookie_import.py # obscura-core extractor (optional extra) / JSON file
├── session_state.py # cookie persistence (~/.config/amazon-lyr/cookies.json)
├── constants.py # endpoints, captcha markers, retry policy
├── exceptions.py, error_handler.py, ratelimit.py, logging_config.py
├── scraping/
│ ├── api_client.py # curl_cffi chrome impersonation; captcha/signin detection;
│ │ # ASIN/order-id validation; return/cancel wizards
│ └── parsers.py # HTML → normalized dicts (bs4, defensive) + review insights
└── tools/
├── search.py, product.py # reads (readOnlyHint=True)
├── reviews.py # get_reviews / insights / keyword scan
├── shopping.py # cart (incl. qty updates)/wishlist/get_orders
├── order_mgmt.py # details/tracking/returns/cancellation
└── session.py # auth status tool
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.
- 5d ago First seen · 85 lines · 954 tokens per session scan A 9ede9aa0db30
amazon-lyr AGENTS.md is an instructions file published in the GitHub repository ishan-parihar/amazon-lyr (0 stars, last pushed 13d ago), licensed MIT. It adds 954 tokens to every session, about $0.0048 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.
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 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.