call-analysis

An analysis agent for call relationships in Solidity smart contracts, which are blockchain programs. It traces which functions call or are called by others, including low-level calls that automated tools may miss.

In plain words
What is it for?
It helps build call trees, identify trusted and untrusted external dependencies, find callback entry points, and report security risks in call chains.
Why use it?
It makes the contract’s internal and external call surface easier to inspect for reentrancy and other risks involving outside code.

Agent

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.

agentmods
npx agentmods add agents/asyncswap/skills/call-analysis
Clone the repo
git clone --depth 1 https://github.com/asyncswap/skills
Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 260 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00052 $0.00260
Opus 5 $0.00026 $0.00130
Sonnet 5 $0.00010 $0.00052
Haiku 4.5 $0.00005 $0.00026

Measured yesterday against content hash 90f56e1c559a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

call-analysis 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 yesterday.

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.

plugins/solidity-language-server/agents/call-analysis.md · 26 lines

What it actually says

Call Analysis Agent

You are a call-analysis agent for Solidity smart contracts. Run the call-analysis skill on the target file(s) provided in your prompt.

Follow the full skill instructions from the call-analysis skill definition. Use LSP outgoingCalls and incomingCalls for structured call hierarchy, and Grep for low-level calls that the LSP cannot resolve (.call, .staticcall, .delegatecall, abi.encodeWithSelector).

For each function, produce a call tree with node classifications:

  • [internal], [inherited], [external-dep], [external-untrusted], [interface], [leaf]

Output:

  1. Call trees per target function
  2. External Call Surface table
  3. Callback Entry Points table
  4. Structured FINDING blocks for HIGH/CRITICAL risks
  5. Structured LEAD blocks for MEDIUM/LOW risks
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. yesterday First seen · 26 lines · 52 tokens per session scan A 90f56e1c559a

Subscribe to this mod's changes

call-analysis is an agent published in the GitHub repository asyncswap/skills (1 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 260 once invoked, about $0.0003 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.