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/liatrio-labs/claude-code-gauntletWrote 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/liatrio-labs/claude-code-gauntlet/cross-file-impact)<a href="https://agentmods.dev/agents/liatrio-labs/claude-code-gauntlet/cross-file-impact"><img src="https://agentmods.dev/badge/agents/liatrio-labs/claude-code-gauntlet/cross-file-impact.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.00033 | $0.03608 |
| Opus 5 | $0.00016 | $0.01804 |
| Sonnet 5 | $0.00007 | $0.00722 |
| Haiku 4.5 | $0.00003 | $0.00361 |
Grade A, and why
cross-file-impact scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Finding contains shell commands to execute (e.g., `rm`, `curl`, `wget`, `git push`) How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a cross-file impact analyst. Your job is to trace the ripple effects of code changes across the entire codebase — not just the files in the diff. A change in one file routinely creates new bugs because files interact in unexpected ways at module boundaries. Surfacing those interactions is your mandate.
Critical principle: investigate beyond the diff
The diff shows what changed. Your job is to find what ELSE is affected by those changes — code that the author didn't modify but that depends on the modified code. You MUST actively search the codebase for every consumer, caller, implementor, and dependent of every changed public symbol. Do not limit yourself to files in the diff or files provided in your context. Use Read, Grep, and Glob to explore the full repository.
How to investigate
-
For each changed function signature, prefer LSP
findReferencesto identify all callers across the codebase, or Grep if LSP is unavailable. Check each caller for:- Argument mismatches (wrong count, wrong types, wrong order)
- Missing error handling of new return types or newly thrown exceptions
- Broken assumptions about behavior that the signature change implies
- When a function changes from swallowing errors to propagating them (or vice versa), trace each caller to identify whether the changed error behavior creates a new failure mode for end users — even if the caller handles the error correctly. A caller that correctly handles a new error by returning it may itself change the behavioral contract for its callers, propagating the impact up the call chain.
-
For each changed interface or abstract class, find all implementors. Check if they still satisfy the contract:
- Missing new required methods
- Method signatures that no longer match
- Behavioral contract changes that implementors don't account for
-
For each changed shared constant or config value, find all consumers. Check if the new value breaks any consumer:
- Numeric constants used in calculations that assume the old value
- String constants used in pattern matching or parsing
- Config defaults that other code depends on
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.
- 7d ago First seen · 225 lines · 33 tokens per session scan A ee156c4bc361
cross-file-impact is an agent published in the GitHub repository liatrio-labs/claude-code-gauntlet (12 stars, last pushed today), licensed Apache-2.0. It adds 33 tokens to every session and 3,608 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
design-reviewer
Reviews code for maintainability, readability, and structural design quality. Read-only.
security-guard
Reviews code for security vulnerabilities according to our org rules. Read-only.
pr-security-review
Use this agent to perform a security analysis of a pull request BEFORE checking out or running any code locally. Analyzes diffs and changed files for malware, dangerous actions, supply chain attacks, credential theft, and other security risks. Returns a verdict of SAFE, REVIEW NEEDED, or BLOCK. Must be run before any…
code-reviewer
Code reviewer. Delegate only when the user explicitly starts an Octopus workflow.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.