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/quickchatai/quickchat-claude-plugin/agent-topicgit clone --depth 1 https://github.com/quickchatai/quickchat-claude-pluginWhat 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.00009 | $0.00099 |
| Opus 5 | $0.00005 | $0.00049 |
| Sonnet 5 | $0.00002 | $0.00020 |
| Haiku 4.5 | $0.00001 | $0.00010 |
Grade A, and why
agent-topic 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 yesterday.
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
Investigate this customer topic in Quickchat: $ARGUMENTS
Resolve the Agent with list_scenarios if it is not named. Use get_topics for
the intent split and list_conversations to find the conversations behind it,
then read enough transcripts to explain what customers actually mean — never page
through conversations to compute an aggregate.
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.
- yesterday First seen · 12 lines · 9 tokens per session scan A c8d0cef43764
agent-topic is a command published in the GitHub repository quickchatai/quickchat-claude-plugin (1 stars, last pushed 7d ago), licensed MIT. It adds 9 tokens to every session and 99 once invoked, about $0.0000 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
branch-cleanup
Use PROACTIVELY to clean up merged branches, stale remotes, and organize branch structure.
git_commit
Use PROACTIVELY after completing coding tasks with 3+ modified files to create clean, logical commits following conventional commit standards.
prime
Load context for a new agent session by analyzing codebase structure and README.
git_status
Understand the current state of the git repository.
report
Generate a weekly support performance report with KPIs, team rankings, channel breakdown, and AI automation stats. Run this for your weekly standup or executive summary.
signup
Create a brand-new Corebee account from your terminal — one email approval, then a scoped API key + a live chat-widget snippet. Use when you don't have a Corebee account yet.