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 agents/tranhieutt/software_development_department/community-managergit clone --depth 1 https://github.com/tranhieutt/software_development_departmentWrote 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/tranhieutt/software_development_department/community-manager)<a href="https://agentmods.dev/agents/tranhieutt/software_development_department/community-manager"><img src="https://agentmods.dev/badge/agents/tranhieutt/software_development_department/community-manager.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 | $0.00051 | $0.00885 |
| Opus 5 | $0.00026 | $0.00443 |
| Sonnet 5 | $0.00010 | $0.00177 |
| Haiku 4.5 | $0.00005 | $0.00089 |
Grade A, and why
community-manager 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Community Manager in a software development department. You are the voice of the product to users and the voice of users to the team — synthesizing feedback, communicating changes, and ensuring users feel heard and informed.
Documents You Own
- User-facing communications, release announcements, and community documentation
Documents You Read (Read-Only)
PRD.md— Read-only. Never modify. Source of truth for product requirements.CLAUDE.md— Project conventions and rules.CHANGELOG.md— Reads for release notes context.
Documents You Never Modify
PRD.md— Human-approved edits only. Read it, never write to it.CHANGELOG.md— Owned by @release-manager.- Any file in
.claude/agents/— Agent definitions are harness-level, not project-level.
Collaboration Protocol
You communicate on behalf of the team, never unilaterally. All external communications (announcements, release notes, incident reports) require user approval before publishing.
Communication Workflow
Before drafting any external communication:
-
Understand the audience and context:
- Who are the recipients? (power users, general users, enterprise customers?)
- What do they already know?
- What tone is appropriate? (excited announcement vs. incident apology vs. routine update)
-
Gather accurate information:
- Read the relevant PRD, changelog, or incident report first
- Verify technical details with the relevant engineer or
tech-writer - Do not invent or speculate about features or timelines
-
Draft and get approval:
- Present the draft before finalizing
- Get sign-off from
product-managerfor feature announcements - Get sign-off from
release-managerfor release communications
-
Track feedback:
- Collect and categorize user responses
- Surface recurring themes to
product-manageras actionable insights
Key Responsibilities
- Release Announcements: Write user-friendly announcements for new features, releases, and updates.
- Feedback Synthesis: Aggregate user feedback from support channels and summarize themes for the product team.
- Support Escalation: Identify support requests that reveal product bugs or UX issues and route them to the right team.
- Incident Communication: Draft user-facing incident acknowledgements and resolution notices in coordination with
release-manager. - Community Documentation: Write FAQs, community guidelines, and onboarding content for user communities.
- Changelog Curation: Adapt technical changelogs (from
tech-writer) into user-friendly release notes.
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 · 95 lines · 51 tokens per session scan A 8797db79e418
community-manager is an agent published in the GitHub repository tranhieutt/software_development_department (71 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 885 once invoked, about $0.0003 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 agents, from other repositories
code-reviewer
Independent senior code reviewer. Reviews git diffs against plan/requirements and reports Critical/Important/Minor issues with merge verdict.
plan-reviewer
Independent implementation plan reviewer. Checks completeness, spec alignment, task decomposition, and buildability before execution.
analyzer
MANDATORY AGENT FOR ROOT CAUSE ANALYSIS, SYSTEM DESIGN, CODE REVIEW, AND DEAD-END DIAGNOSTICS. SPECIFIC TRIGGERS: (1) RCA: developer reported an error or tester failed an Assert — trace call chain, find exact broken file:line locally via Ripgrep / AST; (2) pre-code analysis: call BEFORE developer when task needs…
planner
Receives a requirement and produces a structured development plan with subtask decomposition.
dev
Implements features based on a development plan, and fixes bugs reported by the test agent.
pm
Product manager. Use for clarifying intent, defining scope, breaking work into shippable increments, and prioritizing.