Borrowing it
Nothing to install: this file belongs to zhaoliangbin42/AI-MarkDone. 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/zhaoliangbin42/AI-MarkDone/main/AGENTS.mdgit clone --depth 1 https://github.com/zhaoliangbin42/AI-MarkDoneWrote 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/zhaoliangbin42/ai-markdone/agents-md)<a href="https://agentmods.dev/instructions/zhaoliangbin42/ai-markdone/agents-md"><img src="https://agentmods.dev/badge/instructions/zhaoliangbin42/ai-markdone/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.01351 | $0.01351 |
| Opus 5 | $0.00675 | $0.00675 |
| Sonnet 5 | $0.00270 | $0.00270 |
| Haiku 4.5 | $0.00135 | $0.00135 |
Grade A, and why
AI-MarkDone 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 8d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI-MarkDone Engineering Guide
This repository uses a Codex-first engineering guide for day-to-day development. Keep this file short, stable, and focused on entrypoints.
Project Facts
| Item | Value |
|---|---|
| Product | AI-MarkDone |
| Type | Browser extension |
| Targets | Chrome MV3, Firefox MV2 |
| Runtime surfaces | content runtime, background runtime, extension UI |
| Stack | TypeScript, Vite, Shadow DOM |
| Core constraints | platform adapters, tokenized UI, dual-browser build parity |
Read Order
- This file for repository-wide expectations.
.codex/rules/*for cross-cutting engineering rules..codex/guides/*for task-oriented guidance.- docs/README.md for the long-lived system of record.
- The specific contract or architecture document for the area you are changing.
Common Commands
npm installnpm run test:smokenpm run test:corenpm run build
Non-Negotiables
- Search before editing. Do not assume files, symbols, selectors, or contracts exist.
- Do not use destructive rollback commands such as
git checkout --,git reset --hard, or bulksedreplacements. - UI changes must use the established
--aimd-*token system. Do not hardcode colors, spacing, radius, or z-index values in shipped UI. - Do not use
!importantoutside explicit print-only rules. - Keep architecture changes aligned with the authoritative docs in
docs/. - Any repo-tracked code change must be verified with
npm run buildbefore completion unless the user explicitly waives it.
Required Engineering Behaviors
- Treat user corrections as process failures, not one-off mistakes.
- State what was wrong.
- Adjust the plan or rule you are following.
- Do not repeat the same mistake silently.
- For bug fixes, reproduce the bug with a failing test before changing implementation whenever the bug is testable in this repository.
- If it is not realistically testable, state why and add the closest practical regression check.
- For overlay, modal, popover, panel, or shared-primitive regressions, do not stop at direct surface tests. Also add or update at least one test that enters through the real user-facing trigger path.
- Before writing code for a materially ambiguous request, ask clarifying questions instead of guessing.
- After any code change, explicitly list important edge cases and suggest the tests that should cover them.
- Do not claim success from reasoning alone.
- Use commands, tests, or build output as evidence.
- Prefer the smallest safe change that satisfies the request and preserves current contracts.
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.
- 8d ago First seen · 131 lines · 1,351 tokens per session scan A 27154df69b86
AI-MarkDone AGENTS.md is an instructions file published in the GitHub repository zhaoliangbin42/AI-MarkDone (183 stars, last pushed 12d ago), licensed MIT. It adds 1,351 tokens to every session, about $0.0068 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-30.
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.