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/apptware-product-labs/markr/agents-mdgit clone --depth 1 https://github.com/Apptware-Product-Labs/markrWrote 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/apptware-product-labs/markr/agents-md)<a href="https://agentmods.dev/instructions/apptware-product-labs/markr/agents-md"><img src="https://agentmods.dev/badge/instructions/apptware-product-labs/markr/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.00398 | $0.00398 |
| Opus 5 | $0.00199 | $0.00199 |
| Sonnet 5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
markr 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 5d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 5d ago First seen · 63 lines · 398 tokens per session scan A 355a9eda867d
markr AGENTS.md is an instructions file published in the GitHub repository Apptware-Product-Labs/markr (7 stars, last pushed 18d ago), with no licence file. It adds 398 tokens to every session, about $0.0020 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
dbv-md-reader CLAUDE.md
Claude Code instructions for davidbuenov/dbv-md-reader, covering instrucciones del proyecto para claude code — dbv-md-reader and ⚠️ reglas core.
dbv-md-reader GEMINI.md
Gemini CLI instructions for davidbuenov/dbv-md-reader: This project follows Spec-Driven Development (SDD) with dbv-specs-ops. Read these files at the start of each session before proposing any code or plan.
dbv-md-reader copilot-instructions.md
Copilot instructions for davidbuenov/dbv-md-reader: This project follows Spec-Driven Development (SDD) managed by dbv-specs-ops. Refer to dbv-specs-ops/docs/MASTERPROMPT.md and dbv-specs-ops/docs/SPECIFICATIONS.md. All code edits must comply with the architecture specified in dbv-specs-ops/docs/ARCHITECTURE.md.
markstream-vue AGENTS.md
AGENTS.md instructions for Simon-He95/markstream-vue, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
core copilot-instructions.md
Copilot instructions for asdecided/core: These decisions are already accepted. Do not re-open or contradict them; ask the AsDecided MCP tools (getartifact, searchartifacts) for the full text before proposing a change that touches one.
abap_wiki AGENTS.md
AGENTS.md instructions for Gixsy95/abap_wiki, covering agents.md - abapwiki operating contract, 1. identity and mission, 2. language, 3. architecture: the two planes and 4. inviolable rules.