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/ykorovko/dotagents/agents-mdgit clone --depth 1 https://github.com/ykorovko/dotagentsWhat 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.00112 | $0.00112 |
| Opus 5 | $0.00056 | $0.00056 |
| Sonnet 5 | $0.00022 | $0.00022 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
dotagents 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.
What it actually says
Repository Instructions
This repository contains reusable AI-agent skills.
- Keep each skill self-contained under
skills/<name>/. - Keep skill instructions harness-neutral unless a harness requires different behavior.
- Preserve upstream attribution and license files.
- Record upstream revisions and local adaptations in
THIRD_PARTY_NOTICES.md. - Keep project-specific instructions in downstream repositories.
- Do not add secrets, credentials, customer data, or other private context.
- Run
npx --yes [email protected] add . --listafter changing a skill.
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 · 12 lines · 112 tokens per session scan A 06aef9aad213
dotagents AGENTS.md is an instructions file published in the GitHub repository ykorovko/dotagents (0 stars, last pushed 2d ago), licensed MIT. It adds 112 tokens to every session, about $0.0006 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
pixeltamer-gpt-image-skill CLAUDE.md
Instructions for gabelul/pixeltamer-gpt-image-skill, covering claude.md — pixeltamer, what this is, architecture, how the skill works and the two backends.
ai-agent-skills CLAUDE.md
Instructions for wednesday-solutions/ai-agent-skills, covering project guidelines, wednesday agent skills, available skills, how to use skills and important.
agentic-playwright selectors.instructions.md
Instructions for idavidov13/agentic-playwright, covering selector strategy, critical, instructions, phase 1: open and authenticate and phase 2: explore like a user.
awesome-copilot-id AGENTS.md
Instructions for GulajavaMinistudio/awesome-copilot-id, covering communication, explanation and documentation, markdown formatting, user communication style and workflow & methodology.
llm-ide-rules pytest-integration-tests.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering pytest integration tests and example integration test.
toki AGENTS.md
Instructions for choi138/toki, covering workspace rules, source of truth, toki workflow, required checks and global safety rules.