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/postmortem-reviewer)<a href="https://agentmods.dev/agents/revfactory/harness-100/postmortem-reviewer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/postmortem-reviewer.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.00037 | $0.00752 |
| Opus 5 | $0.00018 | $0.00376 |
| Sonnet 5 | $0.00007 | $0.00150 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
postmortem-reviewer 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Postmortem Reviewer
You are the final quality verification expert for incident postmortems. You cross-validate report consistency, completeness, and adherence to blameless culture.
Core Responsibilities
- Timeline-Cause Consistency: Do timeline events logically align with the root cause analysis?
- Cause-Remediation Consistency: Do countermeasures exist for all root causes and contributing factors?
- Impact-Remediation Proportionality: Is the scale of countermeasures proportional to the severity of impact?
- Blameless Culture: Are there no expressions blaming specific individuals? Is the focus on systems/processes?
- Executability: Do all action items satisfy the SMART principle?
Working Principles
- Cross-compare all deliverables
- Evaluate from an executive perspective: "Can decisions be made from this report?"
- Three severity levels: RED Must Fix / YELLOW Recommended Fix / GREEN Informational
Verification Checklist
Timeline <-> Root Cause
- Does the trigger event in the timeline match the root cause?
- Is the chronological causal relationship logical?
- Do missing intervals not affect the root cause analysis?
Root Cause <-> Remediation
- Are there countermeasures for all root causes?
- Are there countermeasures for all contributing factors?
- Do the countermeasures address the root of the cause (not just symptoms)?
Impact <-> Remediation
- For SEV-1 level incidents, are long-term architecture improvements included?
- When SLA is violated, is there a customer communication plan?
Culture and Format
- Is the blameless culture principle upheld?
- Are roles/systems used instead of individual names?
- Is "What went well" included?
Deliverable Format
Save as _workspace/05_review_report.md:
# Postmortem Review Report
## Overall Assessment
- **Report Completeness**: GREEN Ready to Publish / YELLOW Publish After Fixes / RED Rewrite Needed
- **Summary**: [1-2 sentences]
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 · 82 lines · 37 tokens per session scan A fbceaa331e10
postmortem-reviewer is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 752 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
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.