AgenticAI docs.instructions.md

A set of instructions for writing documentation with clear language, consistent structure, useful headings, and well-formatted Markdown.

In plain words
What is it for?
Use it when writing or reviewing READMEs, guides, code examples, headings, lists, links, and other Markdown documents.
Why use it?
It helps prevent documentation from becoming unclear, disorganized, or difficult to follow.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/marcelroozekrans/agenticai/docs
Clone the repo
git clone --depth 1 https://github.com/MarcelRoozekrans/AgenticAI

Made for: GitHub Copilot.

Per session 414 This file is loaded in full into every session.
When invoked 414 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00414 $0.00414
Opus 5 $0.00207 $0.00207
Sonnet 5 $0.00083 $0.00083
Haiku 4.5 $0.00041 $0.00041

Measured yesterday against content hash e5cbc089c433, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

AgenticAI docs.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 yesterday.

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.

.github/instructions/docs.instructions.md · 88 lines

What it actually says

Documentation Guidelines

Writing Style

Tone & Voice

  • Use clear, concise language
  • Write in active voice
  • Be direct and helpful
  • Avoid jargon unless necessary (define it when used)
  • Use second person ("you") for instructions

Structure

  • Start with a brief overview
  • Use headings to organize content
  • Include table of contents for long documents
  • End with next steps or related resources

Markdown Best Practices

Headings

  • Use sentence case for headings
  • Don't skip heading levels
  • Keep headings descriptive but concise

Code Blocks

  • Always specify the language for syntax highlighting
  • Include comments for complex code
  • Show expected output when helpful
// Example: Creating a new user
const user = await createUser({
  email: '[email protected]',
  name: 'John Doe'
});
// Returns: { id: 'abc123', email: '...', name: '...' }

Lists

  • Use bullet points for unordered items
  • Use numbered lists for sequential steps
  • Keep list items parallel in structure

Links

  • Use descriptive link text (not "click here")
  • Check links periodically for validity
  • Use relative links for internal documentation

Documentation Types

README

  • Project overview and purpose
  • Quick start guide
  • Installation instructions
  • Basic usage examples
  • Links to detailed documentation

API Documentation

  • Endpoint descriptions
  • Request/response examples
  • Authentication requirements
  • Error codes and handling
  • Rate limiting information

Architecture Docs

  • System overview diagrams
  • Component descriptions
  • Data flow explanations
  • Technology decisions and rationale

How-To Guides

  • Clear problem statement
  • Prerequisites
  • Step-by-step instructions
  • Troubleshooting section

Maintenance

  • Review documentation with code changes
  • Date-stamp or version documentation
  • Archive outdated documentation
  • Encourage team contributions
Changes

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.

  1. yesterday First seen · 88 lines · 414 tokens per session scan A e5cbc089c433

Subscribe to this mod's changes

AgenticAI docs.instructions.md is an instructions file published in the GitHub repository MarcelRoozekrans/AgenticAI (1 stars, last pushed 4mo ago), licensed MIT. It adds 414 tokens to every session, about $0.0021 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.

Related

Other instructions, from other repositories

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

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).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens

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.

langchain-ai/langchain · 4,345 tokens