gpt-rag-mcp: Skill for Claude Code

.github/skills/documentation-consistency/SKILL.md

documentation-consistency is a skill for Claude Code, Codex from Azure/gpt-rag-mcp. It costs 39 tokens per session (237 once invoked), scanned A, original, MIT.

A documentation-maintenance workflow for keeping the GPT-RAG MCP service documentation aligned with its actual behavior. It covers setup, capabilities, configuration, deployment, endpoints, defaults, and troubleshooting.

In plain words
What is it for?
Use it when changing features, settings, endpoints, deployment procedures, defaults, or breaking behavior, and when checking whether related service or umbrella documentation must also change.
Why use it?
It prevents instructions from becoming outdated after code or operational changes.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one.

This is Azure/gpt-rag-mcp's own configuration. It tells Claude Code and Codex how to work on gpt-rag-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything gpt-rag-mcp configures →

About the project

Azure/gpt-rag-mcp is a Python server that exposes GPT-RAG capabilities through the Model Context Protocol. It is deployed with Azure resources and consumed by GPT-RAG through its MCP strategy, while the catalogue provides instructions, skills, and agents for operating it.

Azure/gpt-rag-mcp · 22 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to Azure/gpt-rag-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.

Copy the file
curl -O https://raw.githubusercontent.com/Azure/gpt-rag-mcp/main/.github/skills/documentation-consistency/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Azure/gpt-rag-mcp

Made for: Claude Code, Codex.

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

agentmods badge for documentation-consistency

README.md
[![agentmods](https://agentmods.dev/badge/skills/azure/gpt-rag-mcp/documentation-consistency/github.svg)](https://agentmods.dev/skills/azure/gpt-rag-mcp/documentation-consistency)
Your own site
<a href="https://agentmods.dev/skills/azure/gpt-rag-mcp/documentation-consistency"><img src="https://agentmods.dev/badge/skills/azure/gpt-rag-mcp/documentation-consistency/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.

agentmods 80×15 button for documentation-consistency

Your own site · 80×15
<a href="https://agentmods.dev/skills/azure/gpt-rag-mcp/documentation-consistency"><img src="https://agentmods.dev/badge/skills/azure/gpt-rag-mcp/documentation-consistency.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 237 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00039 $0.00237
Opus 5.5 $0.00016 $0.00095
Sonnet 5.5 $0.00008 $0.00047
Haiku 4.5 $0.00004 $0.00024

Measured 2mo ago against content hash d87d23b4e6ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

documentation-consistency 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 2mo 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.

.github/skills/documentation-consistency/SKILL.md · 24 lines

What it actually says

GPT-RAG MCP documentation consistency

  1. Identify the user, orchestrator, or operator behavior that changed.
  2. Search this repository for the capability, configuration key, endpoint, parameter, and previous terminology.
  3. Update service setup and Inspector guidance in README.md and operational diagnosis in TROUBLESHOOTING.md.
  4. If umbrella GPT-RAG deployment, configuration, or user experience changes, search and update the docs branch of Azure/GPT-RAG in the same coordinated change.
  5. Keep repository READMEs focused; link to published GPT-RAG documentation instead of duplicating broad product guidance.
  6. Verify examples against executable defaults and current protocol contracts.
  7. Report every documentation file, branch, or pull request in the implementation handoff.

A visible change is incomplete until documentation is updated or the search demonstrates that no documentation is affected.

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. 2mo ago First seen · 24 lines · 39 tokens per session scan A d87d23b4e6ca

Subscribe to this mod's changes

documentation-consistency is a skill published in the GitHub repository Azure/gpt-rag-mcp (22 stars, last pushed 10d ago), licensed MIT. It adds 39 tokens to every session and 237 once invoked, about $0.0002 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-08-30.

Related

documentation-consistency compared with skills from other repositories

documentation-consistency next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
documentation-consistencyAzure/gpt-rag-mcpSkill2210d agoMITA39Claude Code, Codex
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143ktodayMITA103Claude Code