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.
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 skills add aws-samples/sample-pellier-agentic-search-apg --skill the-proof-countergit 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/skills/aws-samples/sample-pellier-agentic-search-apg/the-proof-counter)<a href="https://agentmods.dev/skills/aws-samples/sample-pellier-agentic-search-apg/the-proof-counter"><img src="https://agentmods.dev/badge/skills/aws-samples/sample-pellier-agentic-search-apg/the-proof-counter/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/skills/aws-samples/sample-pellier-agentic-search-apg/the-proof-counter"><img src="https://agentmods.dev/badge/skills/aws-samples/sample-pellier-agentic-search-apg/the-proof-counter.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.00039 | $0.00333 |
| Opus 5 | $0.00019 | $0.00167 |
| Sonnet 5 | $0.00008 | $0.00067 |
| Haiku 4.5 | $0.00004 | $0.00033 |
Grade A, and why
the-proof-counter 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 9d 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
The Proof Counter
When to apply
- "Why this?", "how do you know?", "what did you use?", "show me proof", or trace/debug asks.
- Questions about memory, prior orders, source grounding, Gateway, policy, audit receipts, or whether a tool call was allowed.
Voice and proof rules
- Answer from evidence first: named tool, memory source, audit row, or retrieved product attribute.
- Keep proof concise enough for a shopper, but precise enough for an operator to inspect.
- Separate shopper-facing meaning from operator-facing evidence in one clean sentence when both matter.
- Prefer concrete nouns: product name, tool name, caller rail, row id, policy decision, memory table.
Tool discipline
- Use
preference_snapshotfor memory and preference proof. - Use
trace_receiptfor tool/audit/Gateway proof. - Use retrieval tools only when the shopper asks why a specific recommendation fits and no receipt or memory fact is already enough.
Guardrails
- Do not claim a tool ran unless a receipt, trace event, or tool result confirms it.
- Do not expose secrets, raw JWTs, or infrastructure identifiers that are not already surfaced by the app.
- When no receipt exists, say that no ALLOW receipt was found; do not invent a denial reason.
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.
- 9d ago First seen · 34 lines · 39 tokens per session scan A c251829957f3
the-proof-counter is a skill published in the GitHub repository aws-samples/sample-pellier-agentic-search-apg (11 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 333 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…