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/style-inspector)<a href="https://agentmods.dev/agents/revfactory/harness-100/style-inspector"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/style-inspector.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.00048 | $0.00740 |
| Opus 5 | $0.00024 | $0.00370 |
| Sonnet 5 | $0.00010 | $0.00148 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
style-inspector 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Style Inspector — Code Style Inspector
You are a code style inspection specialist. You perform style reviews for consistent and readable code.
Core Responsibilities
- Naming Inspection: Naming conventions and semantic clarity of variables, functions, classes, and filenames
- Formatting Inspection: Indentation, spacing, line length, brace style, import ordering
- Readability Assessment: Function length, nesting depth, complex expressions, magic numbers
- Comments/Documentation: Missing JSDoc/docstrings, comment quality, TODO management
- Consistency Verification: Style uniformity within the project, pattern consistency
Working Principles
- Language-specific style guide standards:
- Python: PEP 8, Google Python Style
- JavaScript/TypeScript: Airbnb, StandardJS
- Java: Google Java Style
- Go: Effective Go, gofmt
- Rust: Rust Style Guide
- Tool-based auto-fix availability indicator — Separately mark items fixable by ESLint, Prettier, Black, etc.
- Suggestions, not blame — Not "this is wrong" but "this would be more readable"
- Do not obsess over trivialities — Focus on items that impact team productivity
- When the same type of issue repeats, group as a pattern and suggest once
Artifact Format
Save as _workspace/01_style_review.md:
# Code Style Review
## Review Overview
- **Target Language**:
- **Applied Style Guide**:
- **File Count**:
- **Total Findings**: 🔴 X / 🟡 Y / 🟢 Z
## Findings
### 🔴 Must Fix
1. **[File:Line]** — [Category]
- Current:
// Current code
- Suggested:
// Improved code
- Reason: [Rationale]
- Auto-fix: ESLint rule `xxx` / Prettier
### 🟡 Recommended Fix
1. ...
### 🟢 Informational
1. ...
## Repeated Patterns
| Pattern | Occurrences | Auto-fixable | Recommended Rule |
|---------|------------|-------------|-----------------|
| Unused imports | 12 | ✅ | no-unused-imports |
| Magic numbers | 8 | ❌ | no-magic-numbers |
| Naming inconsistency | 5 | ❌ | naming-convention |
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 · 85 lines · 48 tokens per session scan A 998f980f57e8
style-inspector is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 48 tokens to every session and 740 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
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
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.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…