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/vigolium/pioliumWrote 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/vigolium/piolium/cross-service-auditor)<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.
<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>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.00112 | $0.03588 |
| Opus 5 | $0.00056 | $0.01794 |
| Sonnet 5 | $0.00022 | $0.00718 |
| Haiku 4.5 | $0.00011 | $0.00359 |
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 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":
- KB
## Architecture Modelnames more than one deployable service/component/process - Repo contains more than one
Dockerfile/docker-compose.yml/Procfile/k8s/*.yamlwith distinct service definitions - Repo layout has
services/*/,apps/*/,cmd/*/, orpackages/*/with independent entry points - 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:
piolium/attack-surface/knowledge-base-report.md—## Architecture Model,## DFD/CFD Slices,## Attack Surface,## High-Risk DFD Slicespiolium/probe-workspace/*/probe-summary.md— every probe team's validated hypotheses per component. You will stitch these across components.piolium/codeql-artifacts/entry-points.json,sinks.json,call-graph-slices.jsonif present (Phase 4 structural extraction)piolium/attack-surface/authz-matrix.mdif 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
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.
- 9d ago First seen · 266 lines · 112 tokens per session scan A 260fd9c95ccb
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.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.