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/SaigonXIII/evcWrote 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/saigonxiii/evc/community-harvest)<a href="https://agentmods.dev/commands/saigonxiii/evc/community-harvest"><img src="https://agentmods.dev/badge/commands/saigonxiii/evc/community-harvest.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.00000 | $0.01296 |
| Opus 5 | $0.00000 | $0.00648 |
| Sonnet 5 | $0.00000 | $0.00259 |
| Haiku 4.5 | $0.00000 | $0.00130 |
Grade A, and why
community-harvest scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -H "Authorization: Bot $(cat {{SECRETS_DIR}}/discord-token)" \ How it starts
The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Harvest
Mine community channels (Discord, Slack, Telegram) for recurring questions, pain points, and feature requests. Produces actionable content briefs and documentation gap reports.
Trigger
User invokes /community-harvest or says "harvest community", "what's the community asking", "community insights", "FAQ harvest"
Arguments
- Optional:
--channel <name>— limit to a specific channel - Optional:
--days <N>— lookback period (default: 14) - Optional:
--platform <discord|slack|telegram>— limit to one platform
Steps
1. Gather message history
Scan configured community platforms for the lookback period:
Slack (if Slack MCP available):
- Use
slack_get_channel_historyfor each configured community channel - Include thread replies via
slack_get_thread_repliesfor high-engagement threads (5+ replies)
Discord (if Discord API configured):
# Read from configured Discord channels
# Requires: {{SECRETS_DIR}}/discord-token (bot token)
curl -s -H "Authorization: Bot $(cat {{SECRETS_DIR}}/discord-token)" \
"https://discord.com/api/v10/channels/{{DISCORD_CHANNEL_ID}}/messages?limit=100"
Telegram (if Telegram API configured):
# Read from configured Telegram groups
# Requires: {{SECRETS_DIR}}/telegram-token (bot token)
Manual fallback: If no API access, ask the user to paste or upload a message export file.
2. Filter noise
Remove from analysis:
- Bot messages, automated notifications, welcome messages
- Messages under 10 characters (reactions, "ok", "thanks")
- Duplicate content (cross-posts, reposts)
- Off-topic conversation (greetings, general chat unrelated to product)
3. Extract and classify signals
For each substantive message, classify into:
| Category | Signal | Example |
|---|---|---|
| Question | Direct question about product/service | "How do I set up X?" |
| Pain Point | Frustration, confusion, negative experience | "I keep getting errors when..." |
| Feature Request | Suggestion for new capability | "It would be great if..." |
| Bug Report | Something broken or unexpected | "X doesn't work when Y" |
| Praise | Positive feedback, success story | "Just shipped using X, works great" |
| Comparison | Mentions competitor or alternative | "How does this compare to Z?" |
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.
- 8d ago First seen · 176 lines · 0 tokens per session scan A 7ebf5e4a2711
community-harvest is a command published in the GitHub repository SaigonXIII/evc (56 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,296 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
review-tool
Research a tool or product for skill-gap, architecture, and verb-fit per the Anatomy framework.
setup
First-run setup — replace the fictional company and authors with yours.
review-content
Review content for brand alignment, lead placement, bio consistency, and proof points.
voice-check
Check a draft against the author's voice profile and flag deviations.
content-status
Scan all content directories and report status of drafts, ideas, and published content.
draft-blog
Scaffold a blog post with proper structure, voice, and frontmatter.