Borrowing it
Nothing to install: this file belongs to markoblogo/AGENTS.md_generator. 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/markoblogo/AGENTS.md_generator/main/AGENTS.mdgit clone --depth 1 https://github.com/markoblogo/AGENTS.md_generatorWrote 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/markoblogo/agents.md_generator/agents-md)<a href="https://agentmods.dev/instructions/markoblogo/agents.md_generator/agents-md"><img src="https://agentmods.dev/badge/instructions/markoblogo/agents.md_generator/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/markoblogo/agents.md_generator/agents-md"><img src="https://agentmods.dev/badge/instructions/markoblogo/agents.md_generator/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.01076 | $0.01076 |
| Opus 5.5 | $0.00430 | $0.00430 |
| Sonnet 5.5 | $0.00215 | $0.00215 |
| Haiku 4.5 | $0.00108 | $0.00108 |
Grade A, and why
AGENTS.md_generator 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- AGENTS.md_generator AGENTS.md — 98% identical, 198 lines differ
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file is for coding agents (Codex/Claude/Cursor/etc.). Keep it strict and actionable.
Overview
- Project: AGENTS.md Generator
- Stack: python (vanilla)
- Keep changes small and verifiable.
Repo context
- Project: AGENTS.md Generator
- Stack: python
- Root:
. - Start with:
README.md
- CI:
.github/workflows/
Guardrails
- Work only within the requested scope and preserve local conventions.
- Prefer focused changes; use 300 changed lines as a review signal, not a hard limit.
- Never discard user files, handwritten content, migrations, or data.
- Never hardcode tokens/keys. Never print secrets; document required environment-variable names.
- Run side-effecting or destructive operations only with existing authorization.
- Before changing these areas, confirm intent unless the current task already authorizes it:
- schema changes
- auth/payments/crypto
- deletions or large refactors
- new build tooling/CI changes
- new major dependencies
- A change is complete when behavior, relevant tests, and affected docs agree.
Workflow
- Read the nearest instructions; inspect the current worktree and reproduce the behavior before editing.
- Isolate work when changes overlap or run concurrently; otherwise keep the workflow lightweight and preserve existing user changes.
- Implement the smallest coherent change. Reuse a service layer for genuinely shared mechanics; avoid speculative abstractions.
- Verify the changed behavior with the narrowest useful evidence, then run broader checks appropriate to the change. For visual changes, compare the same important view/state before and after when feasible.
- Update docs and contracts when behavior changes; distinguish local checks from CI, deployment, and release status.
- Report what changed, what evidence passed, and any material limitation. Do not commit, push, or deploy unless requested.
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.
- 1mo ago Changed · +1 lines · +84 tokens per session 907976b1656d
- 1mo ago Changed · -130 lines · -893 tokens per session 7d69b957c87c
- 1mo ago Changed · +6 lines · +72 tokens per session 5603c75e60a4
- 1mo ago First seen · 259 lines · 1,813 tokens per session scan A 5ebdc6bb916f
AGENTS.md_generator AGENTS.md is an instructions file published in the GitHub repository markoblogo/AGENTS.md_generator (5 stars, last pushed 15d ago), licensed MIT. It adds 1,076 tokens to every session, about $0.0043 per session on Opus 5.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
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
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.