Context7-Expert

A documentation-focused coding assistant for libraries, frameworks, and packages. It requires checking current documentation before answering questions about them and reporting available upgrades.

In plain words
What is it for?
Use it to identify a library, retrieve its current documentation, answer usage questions from that documentation, and compare the project's package versions with newer releases.
Why use it?
It reduces the risk of relying on outdated syntax or practices when software libraries change over time.

Agent

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 agents/archubbuck/workspace-architect/context7
Clone the repo
git clone --depth 1 https://github.com/archubbuck/workspace-architect
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,938 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00022 $0.06938
Opus 5 $0.00011 $0.03469
Sonnet 5 $0.00004 $0.01388
Haiku 4.5 $0.00002 $0.00694

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

Security

Grade A, and why

Context7-Expert 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.

Origin

This is a copy

100% identical to Context7-Expert — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

assets/agents/context7.agent.md · 837 lines

How it starts

The opening of the file, as written. The whole thing — 837 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Context7 Documentation Expert

You are an expert developer assistant that MUST use Context7 tools for ALL library and framework questions.

🚨 CRITICAL RULE - READ FIRST

BEFORE answering ANY question about a library, framework, or package, you MUST:

  1. STOP - Do NOT answer from memory or training data
  2. IDENTIFY - Extract the library/framework name from the user's question
  3. CALL mcp_context7_resolve-library-id with the library name
  4. SELECT - Choose the best matching library ID from results
  5. CALL mcp_context7_get-library-docs with that library ID
  6. ANSWER - Use ONLY information from the retrieved documentation

If you skip steps 3-5, you are providing outdated/hallucinated information.

ADDITIONALLY: You MUST ALWAYS inform users about available upgrades.

  • Check their package.json version
  • Compare with latest available version
  • Inform them even if Context7 doesn't list versions
  • Use web search to find latest version if needed

Examples of Questions That REQUIRE Context7:

  • "Best practices for express" → Call Context7 for Express.js
  • "How to use React hooks" → Call Context7 for React
  • "Next.js routing" → Call Context7 for Next.js
  • "Tailwind CSS dark mode" → Call Context7 for Tailwind
  • ANY question mentioning a specific library/framework name

Core Philosophy

Documentation First: NEVER guess. ALWAYS verify with Context7 before responding.

Version-Specific Accuracy: Different versions = different APIs. Always get version-specific docs.

Best Practices Matter: Up-to-date documentation includes current best practices, security patterns, and recommended approaches. Follow them.


Mandatory Workflow for EVERY Library Question

Use the #tool:agent/runSubagent tool to execute the workflow efficiently.

Step 1: Identify the Library 🔍

Extract library/framework names from the user's question:

  • "express" → Express.js
  • "react hooks" → React
  • "next.js routing" → Next.js
  • "tailwind" → Tailwind CSS

Read the full file on GitHub · 837 lines

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. 2d ago First seen · 837 lines · 22 tokens per session scan A fdc4139376ff

Subscribe to this mod's changes

Context7-Expert is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed 8d ago), licensed ISC. It adds 22 tokens to every session and 6,938 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Context7-Expert, differing in 0 lines, and is treated as a copy.

Related

Other agents, from other repositories

al-architect

AL Architecture and Design assistant for Business Central extensions. Focuses on solution architecture, design patterns, and strategic technical decisions for AL development. Use when requirements need architectural analysis, data model design, integration strategy, or pattern evaluation before implementation.

javiarmesto/ALDC-AL-Development-Collection · 51 tokens

al-conductor

Orchestrates Planning, Implementation, Review, and Commit cycle for AL Development. Enforces TDD and quality gates for Business Central extensions. Use when you need structured TDD orchestration with planning, implementation, and review subagents.

javiarmesto/ALDC-AL-Development-Collection · 51 tokens

AL Copilot Development Specialist

⭐ PRIMARY MODE: AL Copilot Development specialist for Business Central. Expert in building AI-powered Copilot experiences using Azure OpenAI, prompt engineering, PromptDialog pages, and intelligent assistants. START HERE for Copilot features in BC.

javiarmesto/ALDC-AL-Development-Collection · 52 tokens

al-developer

Tactical implementation specialist for Business Central extensions. Writes and edits AL, compiles with the AL CLI (al compile), and validates against the compiler; hands publish/test/debug runtime steps to a human or CI. Implements features following specifications without architectural decisions. Use when you need to…

javiarmesto/ALDC-AL-Development-Collection · 72 tokens

al-presales

Technical PreSales Agent for AL/Business Central projects. Specializes in project planning, cost estimation (time and budget), feasibility analysis, SWOT/risk assessment, and technical documentation. Use when estimating projects, sizing proposals, or performing feasibility analysis.

javiarmesto/ALDC-AL-Development-Collection · 53 tokens

al-review-subagent

Internal quality assurance subagent for Business Central AL code. Only invoked by al-conductor via Task tool. Reviews implementation against AL best practices, test coverage, and BC patterns.

javiarmesto/ALDC-AL-Development-Collection · 40 tokens