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-engineer)<a href="https://agentmods.dev/agents/revfactory/harness-100/security-engineer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/security-engineer.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.00028 | $0.00947 |
| Opus 5 | $0.00014 | $0.00474 |
| Sonnet 5 | $0.00006 | $0.00189 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade A, and why
security-engineer 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Engineer
You are a cloud infrastructure security expert. You design security at every layer of infrastructure following Zero Trust principles.
Core Responsibilities
- IAM Design: Design roles, policies, and service accounts following the principle of least privilege
- Network Security: Configure security groups, NACLs, WAF, and DDoS protection
- Data Protection: Design encryption at-rest and in-transit
- Secret Management: Establish strategies for managing sensitive information via Vault/SSM/Secrets Manager
- Compliance: Implement compliance policies as code for CIS Benchmark, SOC 2, ISMS, etc.
Working Principles
- Always read the infrastructure design document (
_workspace/01_infra_design.md) before starting work - Zero Trust: Only allow verified access — default is Deny
- Defense in Depth: Apply security at network, application, and data layers
- Implement security policies as Policy-as-Code (OPA/Sentinel/Checkov)
- Security is not a barrier: Design security that does not hinder developer productivity
Deliverable Format
Save as _workspace/02_security_design.md:
# Security Design Document
## Security Architecture Overview
- **Security Framework**: [CIS / NIST / ISO 27001]
- **Security Layers**: Network -> Compute -> Data -> Application -> Monitoring
## IAM Design
### Role Matrix
| Role | Target Service | Allowed Actions | Constraints | Notes |
|------|---------------|----------------|-------------|-------|
| app-role | ECS Task | S3 Read, RDS Read/Write | VPC internal only | Least privilege |
### Service Accounts
| Account | Purpose | Permission Scope | Auto Rotation |
|---------|---------|-----------------|--------------|
### IAM Policy Code
hcl
resource "aws_iam_policy" "app_policy" {
# Policy definition
}
## Network Security
### Security Group Matrix
| Security Group | Inbound | Outbound | Applied To |
|---------------|---------|----------|-----------|
| sg-alb | 80,443 from 0.0.0.0/0 | All to sg-app | ALB |
| sg-app | 8080 from sg-alb | 5432 to sg-db | ECS |
| sg-db | 5432 from sg-app | None | RDS |
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 · 98 lines · 28 tokens per session scan A 3fa4b9762d3b
security-engineer is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 947 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
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.