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/chenchaozhao/citekick/agents-mdgit clone --depth 1 https://github.com/ChenchaoZhao/citekickWrote 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/chenchaozhao/citekick/agents-md)<a href="https://agentmods.dev/instructions/chenchaozhao/citekick/agents-md"><img src="https://agentmods.dev/badge/instructions/chenchaozhao/citekick/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.01693 | $0.01693 |
| Opus 5 | $0.00847 | $0.00847 |
| Sonnet 5 | $0.00339 | $0.00339 |
| Haiku 4.5 | $0.00169 | $0.00169 |
Grade A, and why
citekick 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 3d 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Initial Exploration
Before writing any code, explore the project structure and understand the conventions:
Read First (Priority Order)
pyproject.toml— Single source of truth for all configurationREADME.md— Project overview and setup instructionsAGENTS.md— Agent-specific instructions if it exists
Extract Key Configuration
From pyproject.toml, identify:
| Setting | Location |
|---|---|
| Package name | [project].name |
| Python version | [project].requires-python |
| Source directory | [tool.hatch.build.targets.wheel] |
| Test directory | [tool.pytest.ini_options].testpaths |
| Max line length | [tool.ruff].line-length |
| Mypy config | [tool.mypy] |
Common Patterns to Match
- Import style and organization
- Type annotation conventions
- Naming conventions (modules, classes, functions)
- Error handling patterns
- Documentation approach
Toolchain Standard
Standard development commands (verify in pyproject.toml):
hatch fmt— Format + lint (ruff)hatch test— Run tests (pytest)hatch run typing— Type check (mypy)hatch run release— fmt + typing + test
Tool Purposes
Ask human to install those tools if they are not installed yet.
| Tool | Purpose |
|---|---|
| hatch | Project and environment management |
| uv | Fast dependency resolution |
| ruff | Linting and formatting |
| mypy | Static type checking |
| pytest | Test execution |
Behavioral Guidelines
Think Before Coding
- State assumptions explicitly. If uncertain, ask.
- If multiple interpretations exist, present them — don't pick silently.
- If a simpler approach exists, say so.
- If something is unclear, stop and ask.
Simplicity First
- No features beyond what was asked.
- No abstractions for single-use code.
- No "flexibility" that wasn't requested.
- If you write 200 lines and it could be 50, rewrite it.
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.
- 3d ago First seen · 245 lines · 1,693 tokens per session scan A 0ec58bf73214
citekick AGENTS.md is an instructions file published in the GitHub repository ChenchaoZhao/citekick (0 stars, last pushed 13d ago), licensed MIT. It adds 1,693 tokens to every session, about $0.0085 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 instructions, from other repositories
deepagents AGENTS.md
AGENTS.md instructions for langchain-ai/deepagents, covering global development guidelines for the deep agents monorepo, corridor security analysis, development workflow, suppressing ruff rules and pr conventions.
apm python.instructions.md
Python development guidelines.
lobster0 AGENTS.md
AGENTS.md instructions for NEDONION/lobster0, covering lobster0 agent 工程规范, 适用范围与优先级, 项目事实, 常用命令 and 首次安装或依赖变化后.
streamlit e2e_playwright.instructions.md
Instructions for streamlit/streamlit, covering streamlit e2e tests, test structure, key fixtures and utilities, external test mode and url handling (no localhost hardcoding).
pydantic-ai-gepa AGENTS.md
AGENTS.md instructions for indexedlabs/pydantic-ai-gepa, covering repository guidelines, mighty workflow, project structure & module organization, build, test, and development commands and coding style & naming conventions.
codexspec CLAUDE.md
Claude Code instructions for Zts0hg/codexspec, covering claude.md - codexspec development guide, project overview, purpose, technology stack and architecture.