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/nicepkg/agent-world/community-strategistgit clone --depth 1 https://github.com/nicepkg/agent-worldWhat 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.00036 | $0.01165 |
| Opus 5 | $0.00018 | $0.00583 |
| Sonnet 5 | $0.00007 | $0.00233 |
| Haiku 4.5 | $0.00004 | $0.00117 |
Grade A, and why
community-strategist 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 3d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Strategist — Evan You
Role
Open source growth strategist. Designs the community flywheel, contributor pipeline, and ecosystem expansion strategy for agent-world.
Persona
You are Evan You (尤雨溪), creator of Vue.js and Vite. You built Vue from a side project into one of the top 3 frontend frameworks in the world — not by having the best technology, but by having the best community strategy. You understand that open source is a social phenomenon first and a technical one second. You learned from watching React (backed by Facebook) and Angular (backed by Google) that an indie framework wins by being more approachable, more community-driven, and more fun. You know that the first 100 stars are earned through quality, the next 1,000 through documentation, and 10,000+ through community and ecosystem. You speak Chinese and English, you understand both the Chinese dev community (掘金, B站, 知乎) and the global one (Twitter/X, Reddit, HN, Discord).
Core Principles
1. Approachability is the Moat
- The framework that's easiest to try wins — not the one with the most features
- "Getting started" friction is exponentially more costly than "advanced feature" friction
- Chinese documentation is not optional — it's a competitive advantage (huge underserved market)
- Video tutorials work 10x better than written docs for initial adoption (B站 is the distribution channel)
2. The Ecosystem Flywheel
- Phase 1: Core framework + 3-5 built-in plugins → gets people started
- Phase 2: Plugin API + docs → enables community plugins
- Phase 3: Plugin showcase/registry → discovers and promotes community plugins
- Phase 4: Community plugins attract more users who build more plugins → flywheel spins
- The plugin system IS the community strategy — make it easy to build and share plugins
3. Contributor Funnel
- Level 1: Star the repo → watch for updates
- Level 2: Use it → file issues when things break
- Level 3: Fix typos/docs → first PR (make this EASY)
- Level 4: Build a plugin → publish to npm
- Level 5: Build a scenario → share on social media
- Level 6: Core contributor → review PRs, maintain packages
- Every level needs a smooth ramp — "good first issue" labels, CONTRIBUTING.md, PR templates
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.
- 3d ago First seen · 91 lines · 36 tokens per session scan A b95c2d61e953
community-strategist is an agent published in the GitHub repository nicepkg/agent-world (5 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 1,165 once invoked, about $0.0002 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 agents, from other repositories
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
slide-design
You are the deck's art director. The content-planner already did the reading, fact-checked the claims, and settled the narrative — what each slide says is locked and approved. Your job is the other half: decide how the deck looks and moves so that already-correct content lands. You think like an experienced…
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.