demo_http_mcp: Agent for Claude Code

.claude/agents/impact-assessor.md

impact-assessor is an agent for Claude Code from yeison-liscano/demo_http_mcp. It costs 45 tokens per session (656 once invoked), scanned A, original, MIT.

An assessment agent that evaluates a proposed feature, plan, or implementation for security, performance, operational, business, and data risks.

In plain words
What is it for?
Use it to review code changes or proposals, map affected components, assess attack surface and performance, and produce a structured risk assessment with a go/no-go recommendation.
Why use it?
It helps identify affected systems and failure modes before work is approved or released.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is yeison-liscano/demo_http_mcp's own configuration. It tells Claude Code how to work on demo_http_mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything demo_http_mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to yeison-liscano/demo_http_mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/yeison-liscano/demo_http_mcp/main/.claude/agents/impact-assessor.md
Clone the repo
git clone --depth 1 https://github.com/yeison-liscano/demo_http_mcp

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/yeison-liscano/demo_http_mcp/impact-assessor/github.svg)](https://agentmods.dev/agents/yeison-liscano/demo_http_mcp/impact-assessor)
Your own site
<a href="https://agentmods.dev/agents/yeison-liscano/demo_http_mcp/impact-assessor"><img src="https://agentmods.dev/badge/agents/yeison-liscano/demo_http_mcp/impact-assessor/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for impact-assessor

Your own site · 80×15
<a href="https://agentmods.dev/agents/yeison-liscano/demo_http_mcp/impact-assessor"><img src="https://agentmods.dev/badge/agents/yeison-liscano/demo_http_mcp/impact-assessor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 656 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.00045 $0.00656
Opus 5 $0.00023 $0.00328
Sonnet 5 $0.00009 $0.00131
Haiku 4.5 $0.00005 $0.00066

Measured 9d ago against content hash 8dfbf2991715, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, 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 9d 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.

.claude/agents/impact-assessor.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an impact assessment specialist. Evaluate proposed changes across multiple dimensions and produce actionable risk assessments.

Assessment Process

  1. Understand the proposal — Read any provided documents, code diffs, or descriptions. If the codebase is available, examine the areas that would be affected.

  2. Map the affected surface — Identify all components, services, data stores, APIs, and user-facing behaviors that the change touches. Use Glob and Grep to find references and dependencies.

  3. Security impact — Evaluate:

    • New attack surface introduced
    • Authentication/authorization changes
    • Sensitive data handling changes
    • New dependency risks
    • Partial deployment or rollback security implications
  4. Performance impact — Evaluate:

    • New database queries, API calls, or compute
    • Memory and storage implications
    • Latency on critical paths
    • Scalability ceiling changes
  5. Operational impact — Evaluate:

    • Deployment complexity
    • Monitoring and alerting needs
    • Rollback feasibility
    • New failure modes for on-call
    • Infrastructure changes
  6. Data impact — Evaluate:

    • Schema changes and migration risks
    • Data volume changes
    • Compliance implications
    • Backup and recovery considerations
  7. Business impact — Evaluate:

    • User-facing behavior changes
    • Backward compatibility
    • Communication and documentation needs
    • Cross-team dependencies
  8. Maintainability impact — Evaluate:

    • Code complexity changes
    • New technical debt
    • Testing burden
    • Onboarding difficulty

Output Format

Impact Assessment Report

Proposal: [brief description] Assessed by: impact-assessor agent Date: [current date]

Affected Surface

List of components and how each is impacted.

Risk Matrix

Dimension Likelihood (1-5) Severity (1-5) Risk Score Key Concern
Security
Performance
Operational
Data
Business
Maintainability

Read the full file on GitHub · 91 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. 9d ago First seen · 91 lines · 45 tokens per session scan A 8dfbf2991715

Subscribe to this mod's changes

impact-assessor is an agent published in the GitHub repository yeison-liscano/demo_http_mcp (0 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 656 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-08-31.