Borrowing it
Nothing to install: this file belongs to dryvist/ai-assistant-instructions. 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/dryvist/ai-assistant-instructions/develop/AGENTS.mdgit clone --depth 1 https://github.com/dryvist/ai-assistant-instructionsWrote 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/dryvist/ai-assistant-instructions/agents-md)<a href="https://agentmods.dev/instructions/dryvist/ai-assistant-instructions/agents-md"><img src="https://agentmods.dev/badge/instructions/dryvist/ai-assistant-instructions/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.1 | $0.00993 | $0.00993 |
| Opus 5 | $0.00496 | $0.00496 |
| Sonnet 5 | $0.00199 | $0.00199 |
| Haiku 4.5 | $0.00099 | $0.00099 |
Grade A, and why
ai-assistant-instructions 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 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.
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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agents Configuration
Coding behavior
- YOU ARE the autonomous orchestrator, owning every task through completion.
- Use evidence, make reasonable assumptions, proceed, and surface only assumptions/tradeoffs that affect action.
- Ship the simplest surgical fix matching existing style; define verifiable success criteria, use the narrowest proof, and report exactly what passed/failed.
For deep design/review/refactor work, use the karpathy-guidelines skill (andrej-karpathy-skills).
Tool choice
Use the best-supported native, third-party, or community solution. Check existing flags and configuration first; the
current implementation often already supports the change. Custom code is the largest anti-pattern because every
custom component creates permanent maintenance. Before writing anything custom, search public code for how the
problem was already solved — grep.app greps a million public repositories, and a pattern with
thousands of hits is idiomatic while one with three is usually a mistake.
Starting any change
Run /refresh-repo, then start in a new worktree.
Git workflow
If the default branch is develop, follow git-flow: PRs target
develop (squash-merge), develop → main by merge commit only. Otherwise use trunk flow. Always make
atomic commits, one fix/feature/section per commit, and load the relevant rule under
agentsmd/rules/on-demand/ before starting that activity. agentsmd/rules/rule-tiers.md is the index:
it maps every activity to the rule that governs it.
Knowledge base
Documentation follows Open Knowledge Format: search relevant concepts before editing, capture new durable knowledge after a change.
Scope
After questions are resolved and the plan is approved, execute end to end in one shot with maximal orchestration. Route side quests and follow-ups to Vikunja; route incidents to Zammad. Never open a GitHub issue. See "Where things get written" below.
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 · -5 tokens per session a01f59e3eb82
- 6d ago First seen · 89 lines · 998 tokens per session scan A c1b6df32c7c9
ai-assistant-instructions AGENTS.md is an instructions file published in the GitHub repository dryvist/ai-assistant-instructions (9 stars, last pushed yesterday), licensed Apache-2.0. It adds 993 tokens to every session, about $0.0050 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
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.
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 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).
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.
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.