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 agentmods add instructions/hampsterx/async-kinesis/agents-mdgit clone --depth 1 https://github.com/hampsterx/async-kinesisWrote 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/hampsterx/async-kinesis/agents-md)<a href="https://agentmods.dev/instructions/hampsterx/async-kinesis/agents-md"><img src="https://agentmods.dev/badge/instructions/hampsterx/async-kinesis/agents-md.svg" alt="Measured on agentmods" 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 | $0.01775 | $0.01775 |
| Opus 5 | $0.00888 | $0.00888 |
| Sonnet 5 | $0.00355 | $0.00355 |
| Haiku 4.5 | $0.00178 | $0.00178 |
Grade A, and why
async-kinesis AGENTS.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 5d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guidance for AI coding agents working in the async-kinesis repository.
This file defines repository-specific operating rules for autonomous or semi-autonomous coding agents. Follow these instructions unless a maintainer explicitly tells you otherwise.
Project Overview
async-kinesis is an AsyncIO-based Python library for producing to and consuming from AWS Kinesis Data Streams. It is published to PyPI as async-kinesis and consumed as a library by downstream services.
- Python: 3.10 - 3.14
- Core deps:
aiobotocore,async-timeout,asyncio-throttle - Optional extras:
redis,dynamodb,prometheus,kpl,msgpack,cli,testing
First Principles
When making changes, follow these priorities:
- Correctness over convenience
- Keep the public API stable (this is a library; downstream consumers depend on it)
- Add tests for new bugs, edge cases, and behaviour changes
- Narrow, focused changes; avoid drive-by refactors
- Prefer editing existing code over introducing new abstractions
Critical rules:
- Do not change public method signatures or exception types without a clear deprecation story
- Do not add backwards-compatibility shims for features that never shipped; just change the code
- Do not silently swallow exceptions, specifically in checkpointer / producer / consumer paths
- Document behaviour changes in the PR body (Summary + Backwards compatibility). Release notes are generated from tagged GitHub releases; there is no
CHANGELOG.md
Package Layout
kinesis/
base.py # Shared async client setup and aiobotocore lifecycle
producer.py # Producer: batching, aggregation, flush
consumer.py # Consumer: shard iteration, checkpointing hook, metrics
checkpointers.py # MemoryCheckPointer, RedisCheckPointer
dynamodb.py # DynamoDBCheckPointer
aggregators.py # KPL aggregation helpers
serializers.py # JSON / msgpack serializers
processors.py # Record post-processing hooks
metrics.py # Metrics collector interface
prometheus.py # Prometheus adapter for metrics
exceptions.py # Public exception types
testing.py # In-memory mock Producer/Consumer + pytest plugin
timeout_compat.py # async-timeout / asyncio.timeout shim across Python versions
utils.py # Shared helpers
cli/ # Optional CLI (install with [cli] extra)
tests/ # Integration + unit tests (Floci + redis for integration)
docs/ # User-facing documentation
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.
- 5d ago First seen · 151 lines · 1,775 tokens per session scan A 7730fd74268d
async-kinesis AGENTS.md is an instructions file published in the GitHub repository hampsterx/async-kinesis (24 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 1,775 tokens to every session, about $0.0089 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 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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.