aws-samples/sample-pellier-agentic-search-apg is an educational reference application for an AI shopping concierge backed by Amazon Aurora PostgreSQL and Amazon Bedrock AgentCore. Its fictional retail storefront turns natural-language shopping requests into catalog searches, specialist-agent decisions, tool calls, and recorded business state, while a companion engineering interface exposes how those operations work. The catalogue add-ons support using or understanding this reference application.
Borrowing it
Nothing to install: this file belongs to aws-samples/sample-pellier-agentic-search-apg. 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/aws-samples/sample-pellier-agentic-search-apg/main/AGENTS.mdgit clone --depth 1 https://github.com/aws-samples/sample-pellier-agentic-search-apgWrote 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/aws-samples/sample-pellier-agentic-search-apg/agents-md)<a href="https://agentmods.dev/instructions/aws-samples/sample-pellier-agentic-search-apg/agents-md"><img src="https://agentmods.dev/badge/instructions/aws-samples/sample-pellier-agentic-search-apg/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.00249 | $0.00249 |
| Opus 5 | $0.00125 | $0.00125 |
| Sonnet 5 | $0.00050 | $0.00050 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
sample-pellier-agentic-search-apg 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 2d 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.
What it actually says
Pellier workshop guardrails for Codex
You are assisting a workshop participant with a bounded coding exercise. Help the participant reason from the repository rather than revealing or reproducing the finished solution.
Working approach
- Inspect the relevant source and surrounding patterns before editing.
- Infer the contract from the code, then briefly explain that contract to the participant before making a change.
- Respect workshop marker comments and make the smallest change contained by those markers.
- Review the resulting diff and use only the verification commands supplied by the lab guide.
- Stop and return control to the participant if the task is blocked or the requested change would exceed the exercise boundary.
Guardrails
- Do not read, copy, or derive an answer from anything under
solutions/unless the participant explicitly chooses the documented fallback path. - Do not modify unrelated files, tests, dependencies, configuration, or infrastructure.
- Do not install packages or run Git commands as part of an exercise.
- Do not turn a one-time exercise solution into reusable automation.
Reusable Codex workflows belong under .Codex/skills/ and are optional
follow-up material, not part of the required participant exercise.
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.
- 2d ago First seen · 30 lines · 249 tokens per session scan A 73258fb6ebec
sample-pellier-agentic-search-apg AGENTS.md is an instructions file published in the GitHub repository aws-samples/sample-pellier-agentic-search-apg (11 stars, last pushed today), licensed MIT. It adds 249 tokens to every session, about $0.0012 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-09-05.
Other instructions, from other repositories
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 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.
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).
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.