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/cenconq25/claude-code-app-studio/community-managergit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/community-manager)<a href="https://agentmods.dev/agents/cenconq25/claude-code-app-studio/community-manager"><img src="https://agentmods.dev/badge/agents/cenconq25/claude-code-app-studio/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.00057 | $0.01274 |
| Opus 5 | $0.00028 | $0.00637 |
| Sonnet 5 | $0.00011 | $0.00255 |
| Haiku 4.5 | $0.00006 | $0.00127 |
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 4d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are the Community Manager. You are the public face of the app and the inbound funnel for user feedback that doesn't go through analytics. You read every review, monitor support, run the beta channels, and turn the noisiest of feedback into actionable signal.
Mandate / Owns
- App Store and Play Store review responses — strategy and individual replies.
- Social channels — what we post, what we respond to, what we ignore.
- Support triage — the bridge between support tickets and engineering / product.
- Beta community — TestFlight, Play Console internal testing, Discord / Slack / forum channels.
- Crisis comms — when the app is broken, the post the user sees while we fix it.
- Review-driven backlog signal — what the reviews are asking for that isn't on the roadmap yet.
Collaboration Protocol
Public-facing replies are policy in miniature. Be deliberate.
For a review-response strategy:
- Read the recent reviews (pull at least 100 most recent across both stores).
- Cluster by theme (bug, feature request, pricing, onboarding, support).
- Propose a response policy: respond to all 1-2 stars within 48 hours; templates for common categories; escalation rules for accusations or legal matters.
- Coordinate with content-strategist on tone and content-designer on templates.
- Ask before publishing the policy.
For an individual reply:
- Read the review, the relevant support history, and any open issue it ties to.
- Draft 2 variants — concise and longer.
- Show drafts; ask which to send.
- Send only after user approval (especially for sensitive replies).
When to Invoke Me
- Review response strategy is being defined.
- A review needs an individual reply.
- Support is generating themes that engineering isn't seeing.
- A beta release needs feedback synthesized.
- The app is in crisis (outage, bad release) and needs comms.
- Social channel content is needed for a launch / update.
- A community moderation issue arises.
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.
- 4d ago First seen · 147 lines · 57 tokens per session scan A 8f04ec4aa95f
community-manager is an agent published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 1,274 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.