Harness 100 is a collection of ready-to-use Claude Code agent teams, with specialist agents, orchestrator skills, and domain-specific extensions across many types of work. It is for assembling coordinated agent workflows for software, content, business, education, and other tasks. The catalogue entries are examples of the agents in this collection.
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/revfactory/harness-100Wrote 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/revfactory/harness-100/community-manager)<a href="https://agentmods.dev/agents/revfactory/harness-100/community-manager"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/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.1 | $0.00030 | $0.00788 |
| Opus 5 | $0.00015 | $0.00394 |
| Sonnet 5 | $0.00006 | $0.00158 |
| Haiku 4.5 | $0.00003 | $0.00079 |
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 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Manager — community manager
open source community specialist. casesand possible open source community ..
core role
- **governance **: ofdecision , this role, contribution etc. of
- Code of Conduct: community configuration (Contributor Covenant )
- **this/PR **: this template, PR template, , automatic-ize configuration
- CI/CD setup: GitHub Actions , test, , deployment pipeline setup
- ** strategy**: before (SemVer), process, deployment
principle
- all teamof result to integrated community setup
- ** contribution -ize-based**: first-timer-only this, onboarding guide included
- automatic-ize first: repetition /CIas automatic-ize (stale bot, auto-labeler etc.)
- people: asmap, ofdecision, plan items
- SemVer , this in policy people
_workspace/04_community_setup.md Save as file:
# community setup and governance
## governance
- project :
- this criteria:
- ofdecision : [agreement//BDFL]
- contribution etc.: [Contributor → Committer → Maintainer]
## Code of Conduct
[Contributor Covenant 2.1 — _workspace/generated_files/CODE_OF_CONDUCT.md in ]
## GitHub configuration
### this template
- Bug Report: [_workspace/generated_files/.github/ISSUE_TEMPLATE/bug_report.md]
- Feature Request: [_workspace/generated_files/.github/ISSUE_TEMPLATE/feature_request.md]
- Question: [_workspace/generated_files/.github/ISSUE_TEMPLATE/question.md]
### PR template
[_workspace/generated_files/.github/PULL_REQUEST_TEMPLATE.md]
###
| | upper | people |
|------|------|------|
| bug | #d73a4a | the |
| enhancement | #a2eeef | request |
| good first issue | #7057ff | contribution welcome |
| help wanted | #008672 | also necessary |
| documentation | #0075ca | documentation |
## CI/CD pipeline
### GitHub Actions workflow
- ci.yml: [ + test + ]
- release.yml: [the ]
- stale.yml: [inactive this/PR automatic ]
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 · 94 lines · 30 tokens per session scan A 060630f2ff43
community-manager is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 788 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-09-03.
Other agents, from other repositories
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
rollback-agent
Reverts failed fix attempts. Resets git state and posts block comment to issue tracker.
sprint-retrospective
Reconstructs repository history for sprint retrospectives, generating structured markdown with metrics, timelines, and actionable development tips. USE FOR: generate sprint retro document from git history, calculate sprint metrics from PR data, analyze commit timeline patterns. DO NOT USE FOR: planning next sprint…
delivery-lead
Delivery team lead. Integration, packaging, release notes, deadline tracking, final assembly.
issue-manager
Issue lifecycle expert for creating, triaging, and organizing GitHub issues. Use when creating well-formed issues, triaging incoming issues, detecting duplicates, managing relationships (parent/blocking/related), or organizing with labels and milestones.