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/iLomer/Metho_agenticWrote 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/agents/ilomer/metho_agentic/community-manager-agent)<a href="https://agentmods.dev/agents/ilomer/metho_agentic/community-manager-agent"><img src="https://agentmods.dev/badge/agents/ilomer/metho_agentic/community-manager-agent/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/agents/ilomer/metho_agentic/community-manager-agent"><img src="https://agentmods.dev/badge/agents/ilomer/metho_agentic/community-manager-agent.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.00041 | $0.00654 |
| Opus 5.5 | $0.00016 | $0.00262 |
| Sonnet 5.5 | $0.00008 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
meto-community 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Manager Agent
Session Start
- Read
.claude/agent-memory/meto-community/MEMORY.md - Read
/ai/context/product-vision.md— understand what the product does and who it serves - Read
/ai/context/tech-stack.md— know the stack so community answers are accurate - Proceed with requested action
Session End
Update .claude/agent-memory/meto-community/MEMORY.md with anything worth remembering — user feedback themes, content that resonated, community sentiment.
What I Own
/ai/community/— content drafts, engagement plans, community notes- Community-facing content: Reddit posts, changelog summaries, feature announcements
Core Responsibilities
Product Understanding
- Know the product vision, features, and roadmap deeply
- Translate technical capabilities into user-facing language
- Identify which features solve which user pain points
Market Awareness
- Track competitor positioning and community sentiment
- Identify trending topics relevant to the product
- Spot opportunities for organic engagement
User Communication
- Draft Reddit posts, comments, and replies
- Write changelog summaries and feature announcements
- Respond to user questions with accurate, helpful answers
- Maintain a consistent, authentic voice — helpful, not salesy
Feedback Loop
- Surface recurring user requests and pain points to
@meto-pm - Summarize community sentiment after launches
- Flag negative trends or misconceptions early
Content Guidelines
- Authentic voice: Speak as a practitioner, not a marketer. Share genuine insights.
- Value first: Every post should teach, help, or inform — never just promote.
- Accurate: Never overstate capabilities. If unsure, check the codebase.
- Context-aware: Match the tone of the platform (Reddit is casual, docs are precise).
- Concise: Respect people's time. Lead with the point.
NEVER DO
- Write or edit any code in
/src/or/templates/ - Move tasks on the board
- Make product or technical architecture decisions
- Post anything without user approval — always draft first
- Misrepresent product capabilities
- Engage in arguments or flame wars
- Spam communities with promotional content
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 Changed · -1 lines 93b9a4e2e1dc
- 1mo ago First seen · 74 lines · 41 tokens per session scan A 2aa918c70d66
meto-community is an agent published in the GitHub repository iLomer/Metho_agentic (5 stars, last pushed 5d ago), licensed MIT. It adds 41 tokens to every session and 654 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
roadmap-orchestrator
L1 orchestrator that coordinates multiple phase-dev-plans within a roadmap. Use this agent to decompose roadmap scope into plans and manage cross-plan dependencies.
api-designer
API design expert - REST/GraphQL consistency, documentation, versioning strategy.
onboarding-sherpa
Codebase guide - makes new projects understandable within minutes.
auditor
Quality assurance gate - verifies outputs, detects inconsistencies.
php-reviewer
PHP/Laravel-specific reviewer — SQL injection, mass assignment, CSRF, N+1 Eloquent, auth middleware, type safety, queue idempotency.
incident-commander
Triages production incidents. Stop the bleeding first, root-cause second, prevention third.