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 commands/aavaz-ai/enterpret-claude-plugins/exploregit 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/commands/aavaz-ai/enterpret-claude-plugins/explore)<a href="https://agentmods.dev/commands/aavaz-ai/enterpret-claude-plugins/explore"><img src="https://agentmods.dev/badge/commands/aavaz-ai/enterpret-claude-plugins/explore.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 | $0.00028 | $0.01470 |
| Opus 5 | $0.00014 | $0.00735 |
| Sonnet 5 | $0.00006 | $0.00294 |
| Haiku 4.5 | $0.00003 | $0.00147 |
Grade A, and why
explore 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/explore
You are exploring your organization's feedback taxonomy and data — the hierarchical classification system for customer feedback. This is a utility command that outputs directly in chat (no report generation).
Pre-Flight
- Check if
context/organization.jsonexists. If not, tell the user: "Run/startfirst to connect to your organization's Knowledge Graph." Stop. - Call
get_organization_detailsfrom theenterpret-wisdom-mcpMCP server. - If it fails with an auth error, tell the user to run
/startand stop. - If successful, read
context/organization.jsonfor org name and L1 categories.
Skills (reference if needed, do NOT read upfront)
wisdom-kg— query patterns and KG rules (only read if a query fails and you need to debug)
Behavior
No argument: Show L1 overview
If the user runs /explore with no argument:
- If
context/organization.jsonalready has L1 categories, present those directly. Otherwise query:
MATCH (nli:NaturalLanguageInteraction)-[:SUMMARIZED_BY]->(fi:FeedbackInsight)-[:HAS_TAGS]->(cft:CustomerFeedbackTags)-[:BELONGS_TO_L1]->(l1:L1)
RETURN l1.name AS category, COUNT(DISTINCT fi.feedback_record_id) AS volume
ORDER BY volume DESC
LIMIT 20
- Present as a numbered table:
| # | Category | Volume |
|---|---|---|
| 1 | {top category} | {volume} |
| 2 | {second category} | {volume} |
| ... | ... | ... |
- Say: "Pick a category number or name to drill deeper, or say 'done' to exit."
With L1 argument: Show L2 breakdown
If the user runs /explore {category} or selects a category:
- Query L2 under that L1:
MATCH (fi:FeedbackInsight)-[:HAS_TAGS]->(cft:CustomerFeedbackTags)-[:BELONGS_TO_L1]->(l1:L1)
MATCH (cft)-[:BELONGS_TO_L2]->(l2:L2)
WHERE l1.name = "{L1_CATEGORY}"
RETURN l2.name AS subcategory, COUNT(DISTINCT fi.feedback_record_id) AS volume
ORDER BY volume DESC
LIMIT 20
- Present as tree + table:
{L1 Category}
├── {L2 subcategory 1} ({volume})
├── {L2 subcategory 2} ({volume})
├── {L2 subcategory 3} ({volume})
└── ...
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.
- 3d ago First seen · 149 lines · 28 tokens per session scan A f496fbf31fbf
explore is a command published in the GitHub repository aavaz-ai/enterpret-claude-plugins (2 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 1,470 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.