Borrowing it
Nothing to install: this file belongs to whitewhiteqq/aws-test-plugin. 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/whitewhiteqq/aws-test-plugin/main/CLAUDE.mdgit clone --depth 1 https://github.com/whitewhiteqq/aws-test-pluginWrote 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/whitewhiteqq/aws-test-plugin/claude-md)<a href="https://agentmods.dev/instructions/whitewhiteqq/aws-test-plugin/claude-md"><img src="https://agentmods.dev/badge/instructions/whitewhiteqq/aws-test-plugin/claude-md/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/instructions/whitewhiteqq/aws-test-plugin/claude-md"><img src="https://agentmods.dev/badge/instructions/whitewhiteqq/aws-test-plugin/claude-md.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.01430 | $0.01430 |
| Opus 5.5 | $0.00572 | $0.00572 |
| Sonnet 5.5 | $0.00286 | $0.00286 |
| Haiku 4.5 | $0.00143 | $0.00143 |
Grade A, and why
aws-test-plugin CLAUDE.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 1mo 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Agent Instructions for aws-test-plugin
This file is read by Claude Code before any operation in this repository.
Follow all rules here in addition to the instructions in src/aws_test_plugin/AGENTS.md.
Commands
# Sync dependencies (after cloning or pulling)
uv sync --locked
# Run all tests
uv run pytest tests/ -v
# Lint — check mode (CI)
uv run ruff check src tests
uv run ruff format --check src tests
# Lint — fix mode (local dev: always fix before format)
uv run ruff check --fix src tests
uv run ruff format src tests
# Type checking — ty is the primary checker (fast, replaces mypy)
uv run ty check src
# Type checking — mypy (secondary; kept for compatibility)
uv run mypy src
# Security scans
uv run bandit -q -c pyproject.toml -r src
# CVE-2026-4539: pygments ReDoS (local-only, no fix yet) — remove ignore once patched
# CVE-2026-25645: requests 2.32.5 — fix in 2.33.0, blocked by exclude-newer cooldown
uv run pip-audit --ignore-vuln CVE-2026-4539 --ignore-vuln CVE-2026-25645
# Verify lockfile is up to date (must pass before any commit)
uv lock --check
# Regenerate lockfile when pyproject.toml changes
uv lock
Change Workflow
Every change, regardless of size, follows this sequence:
- Branch —
git checkout -b feat/<name>orfix/<name>fromdevelop - Implement — make the change
- Docs review — ask: does this change affect README.md, CONTRIBUTING.md, or CLAUDE.md?
- CI/CD changes → update CLAUDE.md (Commands section) if any command changes
- Dependency changes → update README.md and CONTRIBUTING.md if setup steps change
- Workflow/process changes → update CLAUDE.md (relevant section)
src/public API changes → update README.md usage examples
- Version bump — see Version Policy below
- Local checks — must all pass before committing:
uv lock --check uv run ruff check src tests uv run ruff format --check src tests uv run ty check src # or: uv run mypy src uv run pytest tests/ -v uv run bandit -q -c pyproject.toml -r src uv run pip-audit --ignore-vuln CVE-2026-4539 --ignore-vuln CVE-2026-25645 - Commit — conventional commit with full body for non-trivial changes
- PR → develop → main — follow Branch Strategy below
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.
- 1mo ago First seen · 158 lines · 1,430 tokens per session scan A b2b730e178c8
aws-test-plugin CLAUDE.md is an instructions file published in the GitHub repository whitewhiteqq/aws-test-plugin (2 stars, last pushed 25d ago), licensed Apache-2.0. It adds 1,430 tokens to every session, about $0.0057 per session on Opus 5.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 instructions, from other repositories
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.