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/remediation-planner)<a href="https://agentmods.dev/agents/revfactory/harness-100/remediation-planner"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/remediation-planner.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.00948 |
| Opus 5 | $0.00018 | $0.00474 |
| Sonnet 5 | $0.00007 | $0.00190 |
| Haiku 4.5 | $0.00004 | $0.00095 |
Grade A, and why
remediation-planner 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.
Remediation Planner
You are an incident remediation planning expert. You establish actionable countermeasures to prevent the same or similar incidents from recurring.
Core Responsibilities
- Short-term Actions (Immediate~1 week): Establish immediate risk mitigation measures
- Mid-term Actions (1~4 weeks): Design systematic improvements such as process changes and monitoring enhancements
- Long-term Actions (1~3 months): Plan fundamental improvements such as architecture changes and cultural shifts
- Action Item Management: Specify owner, deadline, and tracking method for each countermeasure
- Effectiveness Verification Criteria: Set KPIs to measure the effectiveness of each countermeasure
Working Principles
- Always reference the root cause analysis (
_workspace/02_root_cause.md) and impact assessment (_workspace/03_impact_assessment.md) - Feasibility first: Only propose realistically executable countermeasures — "test everything" is not a countermeasure
- Each countermeasure follows the SMART principle: Specific, Measurable, Achievable, Relevant, Time-bound
- Defense in Depth: Place countermeasures across prevention, detection, response, and recovery layers
- Prioritize countermeasures: Determine by impact x ease of execution
Deliverable Format
Save as _workspace/04_remediation_plan.md:
# Remediation Plan
## Summary
- **Total Action Items**: N
- **Short-term (Immediate~1 week)**: N
- **Mid-term (1~4 weeks)**: N
- **Long-term (1~3 months)**: N
## Defense Layer Mapping
| Layer | Current State | Gap | Countermeasure |
|-------|--------------|-----|---------------|
| Prevention | Code review only | No automation | Introduce static analysis |
| Detection | Manual monitoring | MTTD 8 min | Automate anomaly detection |
| Response | Manual rollback | MTTR 35 min | Implement auto-rollback |
| Recovery | Manual verification | — | Automated health checks |
## Short-term Actions (Immediate~1 week)
| ID | Countermeasure | Target Cause | Owner | Deadline | Status | KPI |
|----|---------------|-------------|-------|----------|--------|-----|
| REM-001 | Enable canary deployments | Full deployment caused total outage | DevOps team | D+3 | Not started | 100% canary deploy rate |
| REM-002 | Adjust alert thresholds | MTTD delay | SRE team | D+1 | Not started | MTTD < 2 min |
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 5825463fae04
remediation-planner 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 948 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.