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/jonny-1812/corebee-mcp-skillsWrote 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/jonny-1812/corebee-mcp-skills/report)<a href="https://agentmods.dev/commands/jonny-1812/corebee-mcp-skills/report"><img src="https://agentmods.dev/badge/commands/jonny-1812/corebee-mcp-skills/report/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/jonny-1812/corebee-mcp-skills/report"><img src="https://agentmods.dev/badge/commands/jonny-1812/corebee-mcp-skills/report.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.00441 |
| Opus 5 | $0.00017 | $0.00220 |
| Sonnet 5 | $0.00007 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
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 10d 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
/corebee:report — Weekly Support Report
Generate a complete support operations snapshot.
Steps
- Call
get_metricswithperiod: "this_week"for dashboard KPIs - Call
get_agent_performancewithperiod: "this_week"for team stats - Call
get_channel_analyticswithperiod: "this_week"for channel breakdown - Call
get_trendswithmetric: "conversations"andperiod: "last_7_days" - Call
get_trendswithmetric: "ai_responses"andperiod: "last_7_days"
Output Format
Support Operations — Weekly Report
Overview
- Open conversations: [count]
- Resolved this week: [count]
- New contacts: [count]
- Total messages: [count]
- AI automation rate: [ai_responses / total_messages]%
Team Performance
| Agent | Assigned | Resolved | Resolution Rate |
|---|---|---|---|
| [Name] | [n] | [n] | [n]% |
Channel Breakdown
| Channel | Conversations | Messages |
|---|---|---|
| [Name] | [n] | [n] |
Trends
- Volume: [increasing/stable/decreasing] vs last week
- AI automation: [improving/stable/declining]
Key Insights
- Top performer, busiest channel, any spikes or anomalies
Rules
- Use agent names from profiles, not IDs
- AI rate = ai_responses / total_messages * 100
- Highlight wins and flag areas needing attention
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.
- 10d ago First seen · 54 lines · 34 tokens per session scan A 4147eea027ab
report is a command published in the GitHub repository jonny-1812/corebee-mcp-skills (0 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 441 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 commands, from other repositories
agent-improve
Audit a Quickchat AI Agent and suggest safe improvements.
agent-launch
Build a new Quickchat AI Agent from a website.
agent-review
Weekly performance review of a Quickchat AI Agent.
agent-topic
Investigate what customers are saying about one topic.
agent-triage
Find and triage Quickchat conversations that need a human.
checklist
Generate a custom checklist for the current feature based on user requirements.