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/timothywarner-org/prompt-pro/markdown-content-instructionsgit clone --depth 1 https://github.com/timothywarner-org/prompt-proWrote 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/timothywarner-org/prompt-pro/markdown-content-instructions)<a href="https://agentmods.dev/instructions/timothywarner-org/prompt-pro/markdown-content-instructions"><img src="https://agentmods.dev/badge/instructions/timothywarner-org/prompt-pro/markdown-content-instructions.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 | $0.00820 | $0.00820 |
| Opus 5 | $0.00410 | $0.00410 |
| Sonnet 5 | $0.00164 | $0.00164 |
| Haiku 4.5 | $0.00082 | $0.00082 |
Grade A, and why
prompt-pro markdown-content-instructions.instructions.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.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Markdown content instructions
Markdown Content Rules
The following markdown content rules are enforced in the validators:
- Headings: Use appropriate heading levels (H2, H3, etc.) to structure your content. Do not use an H1 heading, as this will be generated based on the title.
- Lists: Use bullet points or numbered lists for lists. Ensure proper indentation and spacing.
- Code Blocks: Use fenced code blocks for code snippets. Specify the language for syntax highlighting.
- Links: Use proper markdown syntax for links. Ensure that links are valid and accessible.
- Images: Use proper markdown syntax for images. Include alt text for accessibility.
- Tables: Use markdown tables for tabular data. Ensure proper formatting and alignment.
- Line Length: Limit line length to 400 characters for readability.
- Whitespace: Leave a blank line before and after headings, lists, code blocks, tables, and images to keep the layout readable. Avoid multiple consecutive blank lines.
- Front Matter: Include YAML front matter at the beginning of the file with required metadata fields.
Formatting and Structure
Follow these guidelines for formatting and structuring your markdown content:
- Headings: Use
##for H2 and###for H3. Ensure that headings are used in a hierarchical manner. Place a blank line before each heading and another blank line after it. Recommend restructuring if content includes H4, and more strongly recommend for H5. - Lists: Use
-for bullet points and1.for numbered lists. Indent nested lists with two spaces. Insert a blank line before and after each list. - Code Blocks: Use triple backticks (
) to create fenced code blocks. Specify the language after the opening backticks for syntax highlighting (e.g.,csharp). Leave a blank line before and after each code block. - Links: Use
[link text](URL)for links. Ensure that the link text is descriptive and the URL is valid. - Images: Use
for images. Include a brief description of the image in the alt text. Surround images with blank lines. - Tables: Use
|to create tables. Ensure that columns are properly aligned and headers are included. Provide a blank line before and after each table. - Line Length: Break lines at 80 characters to improve readability. Use soft line breaks for long paragraphs.
- Whitespace: Use blank lines to separate sections and improve readability. Avoid excessive whitespace and trailing spaces.
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 · 56 lines · 820 tokens per session scan A cf8c028d8043
prompt-pro markdown-content-instructions.instructions.md is an instructions file published in the GitHub repository timothywarner-org/prompt-pro (47 stars, last pushed 2mo ago), licensed MIT. It adds 820 tokens to every session, about $0.0041 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
prompts.chat AGENTS.md
AGENTS.md instructions for f/prompts.chat, covering agents.md, project overview, tech stack, project structure and commands.
wanaku CLAUDE.md
Claude Code instructions for wanaku-ai/wanaku, covering wanaku, core guidelines, quick start, build info and architecture.
ase AGENTS.md
AGENTS.md instructions for rse/ase, covering about, repository layout, build system, setup and cli commands.
OpenHands AGENTS.md
AGENTS.md instructions for OpenHands/OpenHands, covering repository notes, general, repository map — what belongs where, cross-repository boundaries and pr description human check.
ai-native-sdlc AGENTS.md
Instructions for bashebr/ai-native-sdlc, covering agents.md, source of truth, validation and conventions.
repo2skill AGENTS.md
Instructions for Hhhkarimi/repo2skill, a project described as: Turn any public GitHub repository into professional, repository-native Agent Skills for ChatGPT and Claude - free, browser-first, no AI API required.