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 agents/azure/gpt-rag/releasegit clone --depth 1 https://github.com/Azure/GPT-RAGWhat 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.00043 | $0.00225 |
| Opus 5 | $0.00022 | $0.00112 |
| Sonnet 5 | $0.00009 | $0.00045 |
| Haiku 4.5 | $0.00004 | $0.00022 |
Grade A, and why
release 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 2d 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.
What it actually says
GPT-RAG release
Follow AGENTS.md, the complete release rules in
.github/copilot-instructions.md, and the multi-repo-release skill.
Read all component and AI Landing Zone versions directly from manifest.json.
Validate that the pinned combination is compatible and that the changelog and
GitHub Release notes describe the same combination. Preserve the required
branch targets, tag format, release title, component table, validation
evidence, and documentation updates.
Never expose personal Azure environment or resource group names. Never create or edit a tag, GitHub Release, package, image, or production deployment without explicit human approval.
Output handoff: proposed version, validated pins, release artifacts changed, validation evidence, documentation status, rollback path, and remaining approval actions.
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.
- 2d ago First seen · 25 lines · 43 tokens per session scan A 594c660e6521
release is an agent published in the GitHub repository Azure/GPT-RAG (1,169 stars, last pushed 15d ago), licensed MIT. It adds 43 tokens to every session and 225 once invoked, about $0.0002 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 agents, from other repositories
triager
Triage old stale issues for obsolescence and recommend closures.
fixer
Fix and verify issues in app.
Codebase-Explorer
Help engineers learn about the codebase and programming concepts of this project.
deployment-specialist
Handles all deployment operations.
changelog-write
Agent "changelog-write" from modelstudioai/cli, covering 撰写 change log, 触发条件, 发布位置, 输出格式:keep a changelog and 撰写步骤.
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.