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/reportgit 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/report)<a href="https://agentmods.dev/commands/aavaz-ai/enterpret-claude-plugins/report"><img src="https://agentmods.dev/badge/commands/aavaz-ai/enterpret-claude-plugins/report.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.00030 | $0.04530 |
| Opus 5 | $0.00015 | $0.02265 |
| Sonnet 5 | $0.00006 | $0.00906 |
| Haiku 4.5 | $0.00003 | $0.00453 |
Grade A, and why
report 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 5d 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 — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/report
You are generating a customer intelligence report. This command auto-detects what kind of report to produce based on the input. Quick modes output directly in chat (with optional doc export); document modes follow a guided archetype workflow for branded output.
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, slug, and citation base URL.
Skills (reference during execution, not upfront)
- User context is loaded from
.local.mdin Pre-Flight; defaults are in thewisdom-kgskill wisdom-kg— read if you need schema details or a query failsreport-engine— read if user requests formatted document outputevidence-synthesis— read when synthesizing quotes and writing the narrative
Query Rules (critical)
- Always use
LIMIT(max 50) - Count with
COUNT(DISTINCT fi.feedback_record_id)— neverCOUNT(nli) - Never use
countas an alias (reserved word) — usevolume - Sentiment values are capitalized:
"Positive","Negative","Neutral" - Dates use string comparison on
record_timestamp:>= "2026-02-27"(notdate()) - Parameter name for
execute_cypher_queryiscypher_query - Never use MATCH after WITH — use a single MATCH with multiple paths
- If no results, say so — never fabricate data
Phase 0: Mode Detection
Parse the user's command and detect mode:
Quick Modes (chat output first, offer doc export after)
/reportor/report weeklyor/report pm→ Weekly Memo mode/report Acme Corpor/report canva→ Account Brief mode/report execor/report leadership→ Executive Summary mode/report USor/report KR→ Regional Digest mode/report cpoor/report engor/report cx→ Weekly Memo mode with audience targeting
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.
- 5d ago First seen · 500 lines · 30 tokens per session scan A da7c9eec1bf8
report is a command published in the GitHub repository aavaz-ai/enterpret-claude-plugins (2 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 4,530 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-31.
Other commands, from other repositories
organize-files
Organize and rename files based on content analysis.
brand-generate
Generate an on-brand document from a saved Brand Profile.
tree
Show file tree with sync status indicators showing which files are indexed, modified, new, or deleted.
prose-review-docs
Reviews markdown documentation files or directories against the active prose style rules — the plugin's vendor-neutral baseline plus your organization's overlay when one is configured. Accepts a file path or directory (recursive). Runs prose-style-checker and optionally Vale. Supports --fix to auto-apply safe…
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.
cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].