Borrowing it
Nothing to install: this file belongs to Dizko-Labs/dizko-mcp. 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/Dizko-Labs/dizko-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/Dizko-Labs/dizko-mcpWrote 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/dizko-labs/dizko-mcp/agents-md)<a href="https://agentmods.dev/instructions/dizko-labs/dizko-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/dizko-labs/dizko-mcp/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/dizko-labs/dizko-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/dizko-labs/dizko-mcp/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.00425 | $0.00425 |
| Opus 5.5 | $0.00170 | $0.00170 |
| Sonnet 5.5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
dizko-mcp 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 7d 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
Git sync rule
These rules keep local checkouts and GitHub in sync across local and cloud sessions. Where this file describes a repo-specific workflow (landing, release, CI, merge gates), that workflow takes precedence.
Before changing files, inspect the working tree and current branch, then run git pull --ff-only on that branch when it has a configured upstream. If the worktree has unrelated changes, the branch is detached or has no upstream, or the pull fails or diverges, stop and report the state. Do not stash, reset, switch branches, force-pull, or overwrite work automatically. Re-read repository guidance after pulling. Pulling updates only this branch's upstream; it does not import another branch or unmerged PR.
After finishing a change, commit it and push so GitHub stays current — don't leave work only on one machine:
- If on the default branch, create a descriptive branch first; never commit or push to the default branch without asking unless this file's workflow says otherwise. Push the branch with an upstream (
git push -u origin <branch>) and offer to open a PR. - On a non-default branch with an upstream, commit and push to it directly.
- If the push is rejected because the remote moved, run
git pull --ff-onlyand push again; if that fails, stop and report. Never force-push, rewrite pushed history, or delete remote branches without asking. - Before ending a task, confirm
git statusis clean and nothing is unpushed; if anything is left behind, say so.
Git security
- Stage files by name, not
git add -A/git add ., and reviewgit diff --stagedbefore committing. - Never commit secrets:
.envfiles, API keys, tokens, private keys, credentials, or service-account JSON. If one is about to be committed, stop and warn; if one is already in history, report it rather than trying to scrub it. - Don't change repo visibility, branch protection, collaborators, or org settings without asking.
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.
- 7d ago First seen · 18 lines · 425 tokens per session scan A 518e6161dc31
dizko-mcp AGENTS.md is an instructions file published in the GitHub repository Dizko-Labs/dizko-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 425 tokens to every session, about $0.0017 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-10-15.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.