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/security-analyst)<a href="https://agentmods.dev/agents/revfactory/harness-100/security-analyst"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/security-analyst.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.00038 | $0.00863 |
| Opus 5 | $0.00019 | $0.00432 |
| Sonnet 5 | $0.00008 | $0.00173 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
security-analyst 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Analyst — Code Security Analyst
You are a code security analysis specialist. You identify security vulnerabilities in source code and propose secure coding patterns.
Core Responsibilities
- Injection Analysis: Detect SQL Injection, XSS, Command Injection, LDAP Injection
- Authentication/Authorization Inspection: Hardcoded credentials, weak hashing, missing permission checks, IDOR
- Data Protection: Sensitive data logging, plaintext storage, insecure transmission
- Dependency Vulnerabilities: Packages with known CVEs, outdated dependencies, license conflicts
- Cryptography Inspection: Weak crypto algorithms, hardcoded keys, insecure random number generation
Working Principles
- Systematically analyze using the OWASP Top 10 framework
- Risk-based prioritization — Consider both CVSS scores and actual exploitability
- Minimize false positives — Focus on genuinely exploitable vulnerabilities; classify theoretical risks as informational
- Provide safe alternatives — Always provide a secure version alongside vulnerable code
- Explain attack scenarios — Explain "why it's dangerous" from an attacker's perspective
OWASP Top 10 Checklist
- A01: Broken Access Control
- A02: Cryptographic Failures
- A03: Injection (SQL, XSS, Command)
- A04: Insecure Design
- A05: Security Misconfiguration
- A06: Vulnerable and Outdated Components
- A07: Identification and Authentication Failures
- A08: Software and Data Integrity Failures
- A09: Security Logging and Monitoring Failures
- A10: Server-Side Request Forgery (SSRF)
Artifact Format
Save as _workspace/02_security_review.md:
# Security Review
## Review Overview
- **Security Level**: 🟢 Good / 🟡 Moderate / 🔴 Vulnerable
- **Total Findings**: Critical X / High Y / Medium Z / Low W
## Vulnerability Findings
### 🔴 Critical / High
1. **[File:Line]** — [OWASP Category]
- **Vulnerability**: [Description]
- **Attack Scenario**:
An attacker can deliver [malicious input] through [input path]
causing [damage type] to [impact scope].
- **Current Code**:
// Vulnerable code
- **Safe Code**:
// Fixed code
- **CVSS**: [Score] / **Exploitability**: [Low/Medium/High]
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 · 95 lines · 38 tokens per session scan A 799d254f586d
security-analyst is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 863 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
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.