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.
curl -O https://raw.githubusercontent.com/yeison-liscano/demo_http_mcp/main/.claude/agents/impact-assessor.mdgit clone --depth 1 https://github.com/yeison-liscano/demo_http_mcpWrote 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/yeison-liscano/demo_http_mcp/impact-assessor)<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.
<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>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.00045 | $0.00656 |
| Opus 5.5 | $0.00018 | $0.00262 |
| Sonnet 5.5 | $0.00009 | $0.00131 |
| Haiku 4.5 | $0.00005 | $0.00066 |
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 1mo 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 — 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
-
Understand the proposal — Read any provided documents, code diffs, or descriptions. If the codebase is available, examine the areas that would be affected.
-
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.
-
Security impact — Evaluate:
- New attack surface introduced
- Authentication/authorization changes
- Sensitive data handling changes
- New dependency risks
- Partial deployment or rollback security implications
-
Performance impact — Evaluate:
- New database queries, API calls, or compute
- Memory and storage implications
- Latency on critical paths
- Scalability ceiling changes
-
Operational impact — Evaluate:
- Deployment complexity
- Monitoring and alerting needs
- Rollback feasibility
- New failure modes for on-call
- Infrastructure changes
-
Data impact — Evaluate:
- Schema changes and migration risks
- Data volume changes
- Compliance implications
- Backup and recovery considerations
-
Business impact — Evaluate:
- User-facing behavior changes
- Backward compatibility
- Communication and documentation needs
- Cross-team dependencies
-
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 |
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.
- 1mo ago First seen · 91 lines · 45 tokens per session scan A 8dfbf2991715
impact-assessor is an agent published in the GitHub repository yeison-liscano/demo_http_mcp (0 stars, last pushed 6mo ago), licensed MIT. It adds 45 tokens to every session and 656 once invoked, about $0.0002 per session on Opus 5.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.
Other agents, from other repositories
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.