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 navendubrajesh/context-management-for-agents --skill amazonq-customizationgit clone --depth 1 https://github.com/navendubrajesh/context-management-for-agentsWrote 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/navendubrajesh/context-management-for-agents/amazonq-customization)<a href="https://agentmods.dev/skills/navendubrajesh/context-management-for-agents/amazonq-customization"><img src="https://agentmods.dev/badge/skills/navendubrajesh/context-management-for-agents/amazonq-customization/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/navendubrajesh/context-management-for-agents/amazonq-customization"><img src="https://agentmods.dev/badge/skills/navendubrajesh/context-management-for-agents/amazonq-customization.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.00087 | $0.01034 |
| Opus 5 | $0.00044 | $0.00517 |
| Sonnet 5 | $0.00017 | $0.00207 |
| Haiku 4.5 | $0.00009 | $0.00103 |
Grade A, and why
amazonq-customization 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Amazon Q Customization
Amazon Q Developer's primary steering surface is .amazonq/rules/ — markdown files (optionally nested) loaded automatically into chat context. The Q CLI supports custom agents and AmazonQ.md scaffolds. This skill covers authoring rules with token budgeting and organizing them for IDE and CLI consistency.
When to Activate
Activate this skill when:
- Creating or restructuring
.amazonq/rules/for IDE or CLI - Organizing rules into subdirectories by domain (frontend, infra, security)
- Writing custom CLI agent definitions for specialized workflows
- Q ignores coding standards or applies backend rules to frontend work
- Responses degrade after the rules library grows
Do not activate this skill for adjacent work owned by other skills:
- Do not activate for
/context showtoken auditing:amazonq-context-architecture. - Do not activate for
/compactand session lifecycle:amazonq-session-management. - Do not activate for platform-agnostic instruction theory:
context-fundamentals. - Do not activate for MCP tool schema design:
tool-design.
Core Concepts
Rule file format
Rules are plain markdown in .amazonq/rules/. No required frontmatter — content is the instruction. Use descriptive filenames (cdk-rules.md, frontend-react.rule.md) for human maintenance; Q loads all .md files regardless of name.
Organize with subdirectories:
.amazonq/rules/
1.project-layout-rules.md
2.project-spec.md
frontend/react.rule.md
infra/cdk.rule.md
Numeric prefixes can enforce human reading order; Q loads all matches.
IDE session toggles
Developers can enable/disable individual rules per chat session via the Rules button. Write rules assuming they may be toggled off — critical invariants should also be enforced by linters/CI.
AmazonQ.md scaffold
Optional root-level AmazonQ.md (or similar) provides project scaffold context alongside README. CLI glob patterns often include it by default — keep concise, behavior-focused.
What ships with it
1 file 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 · 89 lines · 87 tokens per session scan A 2d35e74cf603
amazonq-customization is a skill published in the GitHub repository navendubrajesh/context-management-for-agents (2 stars, last pushed 2mo ago), licensed MIT. It adds 87 tokens to every session and 1,034 once invoked, about $0.0004 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 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…