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/dstrupl/vardoger/agents-mdgit clone --depth 1 https://github.com/dstrupl/vardogerWhat 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.01510 | $0.01510 |
| Opus 5 | $0.00755 | $0.00755 |
| Sonnet 5 | $0.00302 | $0.00302 |
| Haiku 4.5 | $0.00151 | $0.00151 |
Grade A, and why
vardoger 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 2d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering Rules (for AI Assistants)
Authoritative coding instructions for this repository. Linked from:
.cursor/rules/(Cursor).github/copilot-instructions.md(Copilot)CLAUDE.md(Claude Code)AGENTS.md(OpenAI Codex)
Project Structure & Naming
src/vardoger/ # shared core — history reading, analysis, prompt generation
plugins/_shared/ # shared analysis/personalization skill authored once
plugins/cursor/ # Cursor MCP server config, install script
plugins/claude-code/ # Claude Code plugin manifest, skills
plugins/codex/ # Codex plugin manifest, skills
plugins/openclaw/ # OpenClaw skill
plugins/copilot/ # GitHub Copilot CLI plugin manifest, skills
plugins/windsurf/ # Windsurf install snippet and rules delivery
plugins/cline/ # Cline MCP-marketplace manifest + llms-install guide
tests/ # all tests, mirroring src/ structure
| Kind | Path pattern |
|---|---|
| History adapters | src/vardoger/history/<platform>.py |
| Prompt writers | src/vardoger/writers/<platform>.py |
| AI prompts | src/vardoger/prompts/*.md (or plugins/<platform>/prompts/ if platform-specific) |
| Plugin manifests | plugins/<platform>/.<tool>-plugin/plugin.json |
| Skills | plugins/<platform>/skills/<name>/SKILL.md |
| Tests | tests/ directory mirroring src/vardoger/ (e.g., tests/history/test_cursor.py) |
Before You Code
- Find the module boundary: locate the nearest
pyproject.tomland treat it as the unit of build, test, and dependency rules. - Preserve layering: shared core lives in
src/vardoger/, platform-specific code inplugins/<platform>/. Don't mix them. - Prefer configuration over ad-hoc constants: use a config class and env vars rather than scattering
os.getenvcalls. - Avoid duplication: if you see near-identical blocks, centralize them.
Code Review Priorities
These are the patterns reviewers consistently flag:
- Module boundaries & dependency direction
- Shared types belong in
src/vardoger/, not inside a plugin. - Plugin modules should not import from other plugins; dependencies flow inward to the shared core.
- Shared types belong in
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.
- 2d ago First seen · 146 lines · 1,510 tokens per session scan A bc19f4d13d44
vardoger AGENTS.md is an instructions file published in the GitHub repository dstrupl/vardoger (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,510 tokens to every session, about $0.0076 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
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.
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).
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.