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 Amazon-Quick/Amazon-Quick-official-catalog --skill prior-authorization-clinical-policygit clone --depth 1 https://github.com/Amazon-Quick/Amazon-Quick-official-catalogWrote 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/amazon-quick/amazon-quick-official-catalog/prior-authorization-clinical-policy)<a href="https://agentmods.dev/skills/amazon-quick/amazon-quick-official-catalog/prior-authorization-clinical-policy"><img src="https://agentmods.dev/badge/skills/amazon-quick/amazon-quick-official-catalog/prior-authorization-clinical-policy/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/amazon-quick/amazon-quick-official-catalog/prior-authorization-clinical-policy"><img src="https://agentmods.dev/badge/skills/amazon-quick/amazon-quick-official-catalog/prior-authorization-clinical-policy.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.00098 | $0.02802 |
| Opus 5 | $0.00049 | $0.01401 |
| Sonnet 5 | $0.00020 | $0.00560 |
| Haiku 4.5 | $0.00010 | $0.00280 |
Grade A, and why
prior-authorization-clinical-policy 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 10d 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.
The source is not reproduced here
Licensed MIT-0
The repository is licensed MIT-0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 180 lines · 98 tokens per session scan A 3c5ee1908e76
prior-authorization-clinical-policy is a skill published in the GitHub repository Amazon-Quick/Amazon-Quick-official-catalog (48 stars, last pushed 8d ago), licensed MIT-0. It adds 98 tokens to every session and 2,802 once invoked, about $0.0005 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
securing-aws-lambda-execution-roles
Securing AWS Lambda execution roles by implementing least-privilege IAM policies, applying permission boundaries, restricting resource-based policies, using IAM Access Analyzer to validate permissions, and enforcing role scoping through SCPs.
yao-geo-tracking
Build a company-specific GEO backend tracking plan from a company name plus optional supporting information, using authoritative retrieval anchored on the official website, business-feature recognition, and market-aware GEO monitoring methods, then deliver a direct-vs-indirect attribution design, data model, roadmap…
yao-geo-comparison-builder
A tool for creating evidence-based Chinese brand comparison content for AI search and answer platforms. It compares a target brand with competitors, traditional approaches, or self-built solutions.
yao-geo-explainer-builder
A tool for creating detailed, evidence-based educational articles about a topic for Chinese AI search and answer platforms. It can include explanations, how-to steps, selection guidance, common mistakes, FAQs, and a glossary.
yao-deepseek-crawler
Use when a user provides DeepSeek web AI-search keywords, repeat count, target entity, and entity type, then needs repeated fresh-window crawls aggregated into JSON plus a Kami HTML GEO report. Not for generic website crawling, DeepSeek API chat, SEO writing, or one-off answer generation.
yao-geo-brand-graph
A method for building a brand entity knowledge graph from company information, websites, products, customers, people, places, evidence sources, and use cases. A knowledge graph records entities and the supported relationships between them.