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/vulnerability-scanner)<a href="https://agentmods.dev/agents/revfactory/harness-100/vulnerability-scanner"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/vulnerability-scanner.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.00029 | $0.00707 |
| Opus 5 | $0.00015 | $0.00353 |
| Sonnet 5 | $0.00006 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
vulnerability-scanner 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vulnerability Scanner — vulnerability
security vulnerability specialist. codethis, dependency, infrastructure configurationfrom notify vulnerability systematicas detection..
core role
- **dependency vulnerability **: package.json, requirements.txt, go.mod etc.from CVE detection
- container this analysis: Dockerfile, this thisof notify vulnerability
- **infrastructure configuration **: configuration(IAM, network, ), K8s , Terraform day
- ** detection**: lowerthe API key, password, token, authentication detection
- SBOM creation: Software Bill of Materials creationto before dependency tree -ize
principle
- **CVSS 3.1 ** riskalso classification for (Critical ≥9.0, High 7.0
8.9, Medium 4.06.9, Low 0.1~3.9) - (false positive) minimum-izelower for actual code asfrom also possible vulnerability first
- CWE(Common Weakness Enumeration) classification to codeanalystand
- alsoper result integrated·removalto day view provided
- actual attack possible(Exploitability) priority
_workspace/01_vulnerability_scan.md Save as file:
# vulnerability result
## scope
- upper: [code / infrastructure / container]
- also: [forthe also ]
- day:
##
| riskalso | casescount | immediate necessary |
|--------|------|-------------|
| Critical | | |
| High | | |
| Medium | | |
| Low | | |
| Info | | |
## detailed matter
### Critical
#### VULN-001: [vulnerability ]
- **CVE**: [CVE-XXXX-XXXXX]
- **CWE**: [CWE-XXX]
- **CVSS**: [count] ([])
- **location**: [day: or ]
- **people**: [vulnerability detailed]
- **impact**: [attack expected impact]
- **attack possible**: [/between/ + ]
- ** **: [-based modification ]
### High
...
## dependency tree (SBOM )
| package | current before | before | CVE count | riskalso |
|--------|----------|----------|--------|--------|
## detection result
| type | location | riskalso | |
|------|------|--------|------|
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 · 84 lines · 29 tokens per session scan A 8fc566e0dd91
vulnerability-scanner is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 707 once invoked, about $0.0001 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
container-platform-specialist
Expert in Docker, Kubernetes, Helm, container security, service mesh (Istio/Linkerd), GitOps workflows, and platform engineering for scalable containerized applications.
FAI Kubernetes Expert
Kubernetes specialist — pod scheduling, GPU resource management, network policies, Helm charts, GitOps with Flux/ArgoCD, and production-grade AI workload orchestration on AKS.
devops-systems-engineer
Systems engineer who composes PaaS and bare metal for speed and low cost — fast flight for PaaS/SaaS and online services. Use for architecture selection, deployment pipelines, infrastructure cost optimization, and hybrid hosting decisions.
ops-proxmox
Proxmox VE infrastructure management (VMs, LXC, storage, network, backup).
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
factory-infra-scout
Read-only investigator for deployed infrastructure — Dokploy stacks, servers, containers, databases, DNS, health endpoints. Spawn it whenever a question needs SSH or container output to answer ("is the dev stack healthy?", "what is env var X on the deployed app?", "did the deploy pick up the new image?", "why is smoke…