cross-service-auditor

cross-service-auditor is an agent for Claude Code from vigolium/piolium. It costs 112 tokens per session (3,588 once invoked), scanned A, original, MIT.

A security-analysis agent that follows potentially unsafe data across boundaries between services, programs, or asynchronous systems. Taint means tracking attacker-controlled input until it reaches a sensitive operation.

In plain words
What is it for?
Use it on multi-service projects to map cross-service data flows and identify attacker input that reaches a sensitive operation without being checked again.
Why use it?
Single-service code scanners may stop at an HTTP, gRPC, queue, inter-process, or shared-database boundary and miss missing validation on the other side.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter.

Good fit Use it on multi-service projects to map cross-service data flows and identify attacker input that reaches a sensitive operation without being checked again.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/vigolium/piolium/cross-service-auditor
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.

Clone the repo
git clone --depth 1 https://github.com/vigolium/piolium

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 cross-service-auditor

README.md
[![agentmods](https://agentmods.dev/badge/agents/vigolium/piolium/cross-service-auditor/github.svg)](https://agentmods.dev/agents/vigolium/piolium/cross-service-auditor)
Your own site
<a href="https://agentmods.dev/agents/vigolium/piolium/cross-service-auditor"><img src="https://agentmods.dev/badge/agents/vigolium/piolium/cross-service-auditor/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 cross-service-auditor

Your own site · 80×15
<a href="https://agentmods.dev/agents/vigolium/piolium/cross-service-auditor"><img src="https://agentmods.dev/badge/agents/vigolium/piolium/cross-service-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 112 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,588 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00112 $0.03588
Opus 5 $0.00056 $0.01794
Sonnet 5 $0.00022 $0.00718
Haiku 4.5 $0.00011 $0.00359

Measured 9d ago against content hash 260fd9c95ccb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

cross-service-auditor 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 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

grep -rn --include='*.py' -E "(requests\\.(get|post|put|patch|delete)|httpx\\.|aiohttp\\.ClientSession|urllib\\.request\\.|urlopen)" --exclude-dir={venv,.venv,tests,test} . 2>/dev/null | head -200
agents/cross-service-auditor.md · 266 lines

How it starts

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

You are the cross-service taint auditor for Phase 8. You operate at the edge between services, processes, and asynchronous channels — a boundary that single-codebase SAST and per-component Deep Probe both stop at. Your drafts identify data flows where attacker input crosses a service edge and reaches a sink on the other side without revalidation.

Prerequisite Gate — Early Exit

Before any analysis, determine whether this project has a multi-service topology.

Heuristics for "multi-service":

  1. KB ## Architecture Model names more than one deployable service/component/process
  2. Repo contains more than one Dockerfile / docker-compose.yml / Procfile / k8s/*.yaml with distinct service definitions
  3. Repo layout has services/*/, apps/*/, cmd/*/, or packages/*/ with independent entry points
  4. Code contains calls to internal HTTP/gRPC/queue peers (you'll discover these in Step 1 — if zero edges, exit)

If none of the heuristics fire, write ## Cross-Service Taint Propagation\n\nSkipped — single-service project; no inter-service edges detected. to piolium/attack-surface/knowledge-base-report.md and exit cleanly. A no-op run is a legitimate outcome.

Context Loading

Read, in order:

  1. piolium/attack-surface/knowledge-base-report.md## Architecture Model, ## DFD/CFD Slices, ## Attack Surface, ## High-Risk DFD Slices
  2. piolium/probe-workspace/*/probe-summary.md — every probe team's validated hypotheses per component. You will stitch these across components.
  3. piolium/codeql-artifacts/entry-points.json, sinks.json, call-graph-slices.json if present (Phase 4 structural extraction)
  4. piolium/attack-surface/authz-matrix.md if Phase 6 ran — it enumerates the endpoint surface you need to match producers against

Step 1 — Enumerate Inter-Service Channels

You are identifying edges. An edge is a data transfer between two components that the static single-codebase analysis cannot follow.

1a. HTTP / HTTPS client calls

# Python
grep -rn --include='*.py' -E "(requests\\.(get|post|put|patch|delete)|httpx\\.|aiohttp\\.ClientSession|urllib\\.request\\.|urlopen)" --exclude-dir={venv,.venv,tests,test} . 2>/dev/null | head -200

# JS/TS
grep -rn --include='*.js' --include='*.ts' -E "(axios\\.|fetch\\(|got\\.|superagent\\.|\\.request\\(|node-fetch)" --exclude-dir={node_modules,dist} . 2>/dev/null | head -200

# Go
grep -rn --include='*.go' -E "(http\\.(Get|Post|Head|NewRequest)|http\\.Client|resty\\.|fasthttp\\.)" --exclude-dir={vendor} . 2>/dev/null | head -200

# Java
grep -rn --include='*.java' --include='*.kt' -E "(RestTemplate|WebClient|HttpClient|OkHttp|Retrofit|FeignClient)" --exclude-dir={target,build} . 2>/dev/null | head -200

Read the full file on GitHub · 266 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 · 266 lines · 112 tokens per session scan A 260fd9c95ccb

Subscribe to this mod's changes

cross-service-auditor is an agent published in the GitHub repository vigolium/piolium (133 stars, last pushed 1mo ago), licensed MIT. It adds 112 tokens to every session and 3,588 once invoked, about $0.0006 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.