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/agentconnect/awiki-agent-id-message/agents-mdgit clone --depth 1 https://github.com/AgentConnect/awiki-agent-id-messageWrote 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/agentconnect/awiki-agent-id-message/agents-md)<a href="https://agentmods.dev/instructions/agentconnect/awiki-agent-id-message/agents-md"><img src="https://agentmods.dev/badge/instructions/agentconnect/awiki-agent-id-message/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.00650 | $0.00650 |
| Opus 5 | $0.00325 | $0.00325 |
| Sonnet 5 | $0.00130 | $0.00130 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
awiki-agent-id-message 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 — 27 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
scripts/ contains the CLI entry points for identity, messaging, groups, storage, and listener management. Shared SDK logic lives in scripts/utils/. tests/ holds pytest suites and should mirror the module under test, for example tests/test_local_store.py. service/ contains listener deployment templates, and references/ stores protocol, schema, and integration notes. Top-level docs such as README.md, README_zh.md, SKILL.md, and CLAUDE.md explain user flows and agent-facing behavior.
Build, Test, and Development Commands
Use uv for all local development tasks.
uv syncinstalls and locks project dependencies frompyproject.tomlanduv.lock.uv run pytestruns the unit test suite.uv run python scripts/setup_identity.py --listchecks that the CLI and credential loading work.uv run python scripts/check_inbox.py --limit 5is a quick functional smoke test for message retrieval.uv run python scripts/ws_listener.py run --credential default --mode smart --verboseruns the WebSocket listener in the foreground for debugging.
Coding Style & Naming Conventions
Target Python 3.10+ and follow Google-style Python conventions. Use 4-space indentation, explicit type hints on public functions, and short English docstrings where behavior is not obvious. Keep files and functions in snake_case, classes in PascalCase, and constants in UPPER_SNAKE_CASE. Keep CLI wrappers thin; move reusable logic into helper modules such as scripts/utils/ or storage/service helpers.
Testing Guidelines
Tests use pytest. Name files test_*.py and test functions test_*. Prefer focused unit tests with tmp_path, monkeypatch, and temporary SQLite state instead of relying on shared local data. No coverage threshold is enforced in the repository, so contributors should add or update tests whenever they change database schema, query behavior, message routing, or environment-variable based configuration.
When changing feature behavior in this repository, also update the corresponding system tests in the sibling repository at ../awiki-system-test/tests/. Match the system-test location to the changed module's parent area whenever possible, such as tests/cli/, tests/did/, or tests/listener/.
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 · 27 lines · 650 tokens per session scan A d32c660bdf55
awiki-agent-id-message AGENTS.md is an instructions file published in the GitHub repository AgentConnect/awiki-agent-id-message (18 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 650 tokens to every session, about $0.0032 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.
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).
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.
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.