Borrowing it
Nothing to install: this file belongs to Sidd27/infrawise. 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/Sidd27/infrawise/main/AGENTS.mdgit clone --depth 1 https://github.com/Sidd27/infrawiseWrote 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/sidd27/infrawise/agents-md)<a href="https://agentmods.dev/instructions/sidd27/infrawise/agents-md"><img src="https://agentmods.dev/badge/instructions/sidd27/infrawise/agents-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/sidd27/infrawise/agents-md"><img src="https://agentmods.dev/badge/instructions/sidd27/infrawise/agents-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.11221 | $0.11221 |
| Opus 5.5 | $0.04488 | $0.04488 |
| Sonnet 5.5 | $0.02244 | $0.02244 |
| Haiku 4.5 | $0.01122 | $0.01122 |
Grade C, and why
infrawise AGENTS.md scanned grade C with 1 finding 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 yesterday.
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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
- **NO source code changes for local emulators — period.** `src/` is written for real AWS only. LocalStack and Floci are both reached through a standard AWS profile the user adds to their global `~/.aws/config` + `~/.aws How it starts
The opening of the file, as written. The whole thing — 622 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infrawise — AI instructions
Project goal
Genesis pain: Developers had to copy-paste DynamoDB schemas, RDS table definitions, and Lambda trigger shapes from the AWS console into their AI coding assistant every single session. Manual, repetitive, breaks flow, and still produces wrong code because the pasted context is incomplete.
What Infrawise is: The canonical tool for infra-aware AI coding. When a developer thinks "how does my AI assistant know my DynamoDB schema without me pasting it?" — the answer should be Infrawise. The positioning goal is to own the "infra-aware AI coding" category the way Prettier owns formatting or Husky owns git hooks.
Two product pillars:
Context (developer experience) — AI coding assistants know your live infrastructure. Exact partition keys, sort keys, GSIs, Lambda trigger event shapes, queue DLQ coverage, API routes and their Lambda bindings. The developer never looks at the AWS console mid-coding again. Write correct code the first time because the AI already knows the schema.
Guard (mistake prevention) — Surface costly infra mistakes before they ship. Wrong SQS visibility timeout causing duplicate Lambda processing. Missing DLQ silently dropping failed messages. A Lambda scanning a DynamoDB table without a GSI. RDS queries on unindexed columns. These are expensive to discover in production. Infrawise warns at coding time, not incident time.
What it covers today:
- AWS: DynamoDB, Lambda, SQS, SNS, SSM Parameter Store, Secrets Manager, EventBridge, RDS, API Gateway, S3, CloudWatch Logs, Cognito, Kinesis, MSK (clusters), ElastiCache, CloudFront, CloudWatch metrics (opt-in runtime signals)
- Databases: PostgreSQL, MySQL, MongoDB
- Messaging: Apache Kafka via
kafkajs(TS/JS) and kafka-python/confluent-kafka (Python) — broker-agnostic (self-hosted, Confluent, Redpanda, or Amazon MSK). Producer/consumer-to-topic mapping is extracted from application code (AST scan, always-on, no config key) and surfaced as topic nodes viaget_topic_details. Distinct from the Amazon MSK Lambda trigger (detected from the event-source ARN, with event shapeevent.records[topic][0].value). - IaC: Terraform, CDK, CloudFormation (local file parsing for drift detection, plus stack outputs / cross-stack exports)
- Code scanning: TypeScript/JavaScript (ts-morph) and Python (bundled stdlib-ast scanner run via python3 subprocess, requires python3 on PATH) — auto-detected by file signal, no config. Python detection: boto3 clients and
dynamodb.Table()resources,cursor.execute/SQLAlchemytext()SQL, pymongo collections, kafka-python/confluent-kafka
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.
- yesterday Changed · +3 lines · +163 tokens per session f95e107576ae
- 8d ago Changed · +21 lines · +862 tokens per session d47d6e545524
- 16d ago Changed · +2 lines · +101 tokens per session e526d57ea7c5
- 18d ago Changed · +16 tokens per session 49cfcc9338a4
- 1mo ago Changed · +42 tokens per session 05409a767092
- 1mo ago Changed · +5 lines · +470 tokens per session d207b93f6e20
- 1mo ago First seen · 591 lines · 9,567 tokens per session scan C 9deebcc68632
infrawise AGENTS.md is an instructions file published in the GitHub repository Sidd27/infrawise (22 stars, last pushed yesterday), licensed MIT. It adds 11,221 tokens to every session, about $0.0449 per session on Opus 5.5. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.