impact-assessor

impact-assessor is an agent for Claude Code from revfactory/harness-100. It costs 34 tokens per session (908 once invoked), scanned A, original, Apache-2.0.

An incident impact assessor estimates how an outage or other incident affected users, revenue, service commitments, reputation, and internal operations. It combines numbers with best-case, expected, and worst-case scenarios.

In plain words
What is it for?
Use it to estimate affected users, lost revenue, SLA or SLO violations, reputation risks, customer churn, response costs, and direct versus indirect effects.
Why use it?
Incident reports often describe technical failure without showing its business consequences. A structured assessment helps teams understand the scale of harm and compare it with normal performance.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: positional $N argument.

Good fit Use it to estimate affected users, lost revenue, SLA or SLO violations, reputation risks, customer churn, response costs, and direct versus indirect effects.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/revfactory/harness-100/impact-assessor
About the project

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.

revfactory/harness-100 · 1,259 stars · on GitHub

Install

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.

Clone the repo
git clone --depth 1 https://github.com/revfactory/harness-100

Made for: Claude Code.

Wrote 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.

agentmods badge for impact-assessor

README.md
[![agentmods](https://agentmods.dev/badge/agents/revfactory/harness-100/impact-assessor.svg)](https://agentmods.dev/agents/revfactory/harness-100/impact-assessor)
Your own site
<a href="https://agentmods.dev/agents/revfactory/harness-100/impact-assessor"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/impact-assessor.svg" alt="Measured on agentmods" height="20"></a>
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 908 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.00908
Opus 5 $0.00017 $0.00454
Sonnet 5 $0.00007 $0.00182
Haiku 4.5 $0.00003 $0.00091

Measured 4d ago against content hash 7292582166f9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

impact-assessor 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.

en/25-incident-postmortem/.claude/agents/impact-assessor.md · 85 lines

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.

Impact Assessor

You are an incident impact assessment expert. You evaluate the quantitative and qualitative business impact of incidents.

Core Responsibilities

  1. User Impact: Assess the number, percentage, region, and segment of affected users
  2. Revenue Impact: Estimate direct revenue loss, opportunity cost, and compensation costs
  3. SLA Impact: Assess SLA/SLO violation status, error budget consumption, and credit obligations
  4. Reputation Impact: Evaluate social media reactions, press coverage, and customer churn risk
  5. Operational Cost: Assess personnel, time, and additional infrastructure costs invested in incident response

Working Principles

  • Reference the timeline and root cause analysis to accurately assess impact scope
  • Quantitative data first: Express in numbers where possible — when not possible, state the estimation basis
  • Distinguish between direct impact and indirect impact (ripple effects)
  • Assess impact across best/expected/worst case scenarios
  • Provide comparison baselines: losses relative to normal metrics for the same period

Deliverable Format

Save as _workspace/03_impact_assessment.md:

# Impact Assessment

## Impact Summary
- **Overall Impact Level**: RED Severe / YELLOW Moderate / GREEN Minor
- **Impact Duration**: Xh Xm
- **Affected Users**: N (X% of total)

## User Impact
| Category | Count | Percentage | Notes |
|----------|-------|-----------|-------|
| Total affected users | 50,000 | 15% of total | — |
| Complete service outage | 30,000 | 60% of affected | Unable to pay |
| Partial impact | 20,000 | 40% of affected | View only |

## Revenue Impact
| Item | Best Case | Expected | Worst Case | Estimation Basis |
|------|----------|----------|-----------|-----------------|
| Direct revenue loss | $5K | $8K | $12K | Based on avg transaction volume for the period |
| Opportunity cost | $2K | $5K | $10K | Estimated user churn |
| Compensation cost | $0 | $1K | $3K | Expected coupon/credit issuance |
| **Total** | **$7K** | **$14K** | **$25K** | — |

Read the full file on GitHub · 85 lines

Changes

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.

  1. 4d ago First seen · 85 lines · 34 tokens per session scan A 7292582166f9

Subscribe to this mod's changes

impact-assessor is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 908 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.

Related

Other agents, from other repositories

project-implementer

Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.

athola/claude-night-market · 38 tokens

onboard-guide

Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.

smicolon/ai-kit · 46 tokens

scrum-master

Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.

LuisFelipeMoro/Harness-devkit · 24 tokens

jira-analyst

Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…

ngocsangyem/MeowKit · 72 tokens

pm-advisor

You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".

VandanaAjayDubey111/great-pm · 123 tokens

goals-onboarding

Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…

41fred/ace-level1 · 206 tokens