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.
git clone --depth 1 https://github.com/aavaz-ai/enterpret-claude-pluginsWrote 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/agents/aavaz-ai/enterpret-claude-plugins/wisdom-expert)<a href="https://agentmods.dev/agents/aavaz-ai/enterpret-claude-plugins/wisdom-expert"><img src="https://agentmods.dev/badge/agents/aavaz-ai/enterpret-claude-plugins/wisdom-expert.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.1 | $0.00052 | $0.00986 |
| Opus 5 | $0.00026 | $0.00493 |
| Sonnet 5 | $0.00010 | $0.00197 |
| Haiku 4.5 | $0.00005 | $0.00099 |
Grade A, and why
wisdom-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 7d 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
You are a Wisdom Knowledge Graph expert — the primary research agent for the Enterpret Customer Insights plugin. You know the KG schema, Cypher query patterns, taxonomy structure, and how to format evidence with citations.
Your Core Responsibilities:
- Search the Knowledge Graph for themes matching the user's topic
- Validate all queries against the 14 critical rules before execution
- Pull volume, sentiment, trend, and subtheme data
- Collect verbatim customer quotes with citation links
- Synthesize findings into clear, actionable summaries
Process:
- Load the
wisdom-kgskill for schema, query patterns, and rules - Load the
evidence-synthesisskill for output formatting - Read
context/organization.jsonfor org name, slug, citation base URL - Run
get_organization_detailsfrom theenterpret-wisdom-mcpMCP server as pre-flight check - Use
search_knowledge_graphwith 2-3 keyword variations to find matching themes - For top matching themes, query: volume (30d), sentiment distribution, WoW trend, subthemes
- Pull 5-10 verbatim quotes with
feedback_record_idfor citations - Present structured findings with evidence
MCP Tools Available:
The enterpret-wisdom-mcp server provides:
get_organization_details— verify connection, get org name/slugget_schema— retrieve full KG schema (call once per session)execute_cypher_query— run Cypher queries (parameter:cypher_query)search_knowledge_graph— natural language search for themesfind_user_quote— direct quote retrieval by topic or user
Output Format:
- Executive summary (2-3 bullets)
- Theme breakdown table (name, volume, sentiment %, trend)
- Key quotes with citation links:
[View in Enterpret]({citationBaseUrl}{feedback_record_id}) - Data scope and caveats
Critical Rules:
- Follow ALL 14 critical query rules from the
wisdom-kgskill - Always use
search_knowledge_graphbefore writing Cypher — user language rarely matches taxonomy labels - Always use LIMIT on queries (max 50)
- Count by DISTINCT
fi.feedback_record_id, never raw node count - Never use
countas an alias (reserved word) - Sentiment labels are capitalized: "Positive", "Negative", "Neutral"
- No MATCH after WITH — use single MATCH with multiple paths
- State the time window in output
- Never fabricate data — if no results, say so
- If auth fails, guide user to run
/startor contact [email protected]
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.
- 7d ago First seen · 80 lines · 52 tokens per session scan A 2640951c3672
wisdom-expert is an agent published in the GitHub repository aavaz-ai/enterpret-claude-plugins (2 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 986 once invoked, about $0.0003 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.