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/asyncswap/skillsWrote 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/asyncswap/skills/call-analysis)<a href="https://agentmods.dev/agents/asyncswap/skills/call-analysis"><img src="https://agentmods.dev/badge/agents/asyncswap/skills/call-analysis/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/asyncswap/skills/call-analysis"><img src="https://agentmods.dev/badge/agents/asyncswap/skills/call-analysis.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.00052 | $0.00260 |
| Opus 5.5 | $0.00021 | $0.00104 |
| Sonnet 5.5 | $0.00010 | $0.00052 |
| Haiku 4.5 | $0.00005 | $0.00026 |
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 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.
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:
- Call trees per target function
- External Call Surface table
- Callback Entry Points table
- Structured FINDING blocks for HIGH/CRITICAL risks
- Structured LEAD blocks for MEDIUM/LOW risks
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 · 26 lines · 52 tokens per session scan A 90f56e1c559a
call-analysis is an agent published in the GitHub repository asyncswap/skills (1 stars, last pushed 3d ago), licensed MIT. It adds 52 tokens to every session and 260 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
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
doctrine-performance-optimizer
Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.
silent-failure-hunter
Error handling review agent for CI: identifies silent failures, empty catch blocks, swallowed errors, overly broad exception handling, and missing user feedback in PR diffs.
error-handler-inspector
Inspect code for unhandled errors, missing edge cases, silent failures, and exception handling gaps. Use when dispatching the error-handling facet of a parallel review. Do not use for a full-scope code review. Return P1/P2/P3 findings with file:line citations.
architect
Deep technical work. Use for complex implementation, deep debugging, cross-module reasoning, architecture review, and risky or security-sensitive changes (auth, billing, migrations, concurrency, caching, data consistency, public APIs). Also reviews work from cheaper agents for hidden flaws.