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/lfglabs-dev/awesome-amp-code/agents-mdgit clone --depth 1 https://github.com/lfglabs-dev/awesome-amp-codeWhat 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.00385 | $0.00385 |
| Opus 5 | $0.00192 | $0.00192 |
| Sonnet 5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
awesome-amp-code 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
Agent Guidelines for awesome-amp-cli Repository
Build, Lint & Test Commands
- Lint readme:
npx awesome-lint readme.md - Link check:
awesome_bot --allow-redirect --white-list https://github.com/lfglabs-dev/awesome-amp-code,https://example.com readme.md - Node.js version: Use v21.6.0 (as specified in .tool-versions)
Code Style Guidelines
- Markdown Format: Follow standard Markdown formatting for documentation
- List Items: Add items at the bottom of existing lists
- Item Format:
- [item name](https link) - Description beginning with capital, ending in period. - Commits: Always create a new branch for proposed changes
- PR Process: Check spelling and grammar before submitting
- Code of Conduct: All contributions must adhere to the Code of Conduct
Project Structure
- Documentation is the primary focus of this repository
- Main content is in amp_cli_docs.md and readme.md
- CI pipeline uses awesome-lint and awesome_bot to validate content
Add link to Projects & Tools section
When /builtwith followed by a link is included in a prompt, you will add the link to the "Projects & Tools" section of the README.md file under the appropriate subcategory (Documentation & Guides, Development Tools, Applications Built with Amp, or Browser & Misc). If there is a numbered list of urls, create subagents to complete the tasks.
Add link to @docs/amp_faq.md
When /faq followed by a link is included in a prompt, you will add the link to the @docs/amp_faq.md file in between --- and --- Place it above the last question. The update the Last Modified date
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 · 31 lines · 385 tokens per session scan A 93f73aeb0947
awesome-amp-code AGENTS.md is an instructions file published in the GitHub repository lfglabs-dev/awesome-amp-code (77 stars, last pushed 6mo ago), licensed CC0-1.0. It adds 385 tokens to every session, about $0.0019 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-30.
Other instructions, from other repositories
awesome-go AGENTS.md
Instructions for avelino/awesome-go, covering awesome-go · llm contribution guide, project snapshot, when modifying the awesome list, coding guidelines and testing & validation.
awesome-ChatGPT-repositories CLAUDE.md
Instructions for taishi-i/awesome-ChatGPT-repositories, covering awesome-chatgpt-repositories — claude code guide, repository structure, plugin skill (when installed via /plugin), local standalone command (when repo is cloned) and compact data format (plugins/awesome-chatgpt-search/data/).
awesome-vscode CLAUDE.md
Instructions for viatsko/awesome-vscode, covering claude.md, what this repo is, adding an entry, themes and linting / ci.
awesome-python AGENTS.md
AGENTS.md instructions for vinta/awesome-python, covering agents.md and entry rules.
awesome-python CLAUDE.md
Claude Code instructions for vinta/awesome-python, covering claude.md and entry rules.
awesome-quant AGENTS.md
AGENTS.md instructions for wilsonfreitas/awesome-quant, covering agents.md, project overview, architecture, commands and install deps (requires python 3.11+).