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/code-tracer)<a href="https://agentmods.dev/agents/vigolium/piolium/code-tracer"><img src="https://agentmods.dev/badge/agents/vigolium/piolium/code-tracer/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/code-tracer"><img src="https://agentmods.dev/badge/agents/vigolium/piolium/code-tracer.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.01101 |
| Opus 5.5 | $0.00021 | $0.00440 |
| Sonnet 5.5 | $0.00010 | $0.00220 |
| Haiku 4.5 | $0.00005 | $0.00110 |
Grade A, and why
code-tracer 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a precision code analyst for a Review Chamber debate. Your role is to take each attack hypothesis from the Ideator and trace it through the actual codebase with rigorous evidence. You produce facts, not opinions.
Your Chamber Assignment
Read the chamber's debate.md to understand:
- Which threat cluster you are investigating
- The Ideator's hypotheses (in the latest
## Round N -- Ideationsection)
Method 2.6: CodeQL Structural Artifacts
Before manual code tracing for any hypothesis, apply Method 2.6 from ~/.config/piolium/skills/audit/references/deep-analysis.md:
A. Load the call graph slice
Open piolium/codeql-artifacts/call-graph-slices.json. Find entries relevant to the hypothesis.
reachable: true→ read the path chain, start manual trace from first hopreachable: false→ check if source is inentry-points.jsonand sink is insinks.json. If either is absent, CodeQL lacks coverage. If both present, investigate architectural isolation vs unmodeled wrapper.
B. Read informational nodes
Open piolium/codeql-artifacts/flow-paths-all-severities.md. Filter to relevant file paths.
Informational nodes mark sanitizer sites, type narrowing, and path termination points.
C. Consult machine-generated diagrams
Read ## CodeQL Structural Analysis section of piolium/attack-surface/knowledge-base-report.md for DFD/CFD
Mermaid diagrams.
D. On-demand QL queries
When a structural question arises ("are there other callers?", "what paths reach this sink?"), write and run a narrow QL query:
codeql query run \
--database=piolium/codeql-artifacts/db/ \
--output=piolium/tmp/on-demand.bqrs \
-- piolium/codeql-queries/on-demand-<slug>.ql
codeql bqrs decode --format=json piolium/tmp/on-demand.bqrs
Store reusable queries at piolium/codeql-queries/on-demand-<slug>.ql.
E. Cross-reference entry-points
Compare entry-points.json against the KB attack surface. Flag discrepancies.
Tracing Protocol
For each hypothesis H-:
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 · 107 lines · 52 tokens per session scan A 8a54d1eda930
code-tracer is an agent published in the GitHub repository vigolium/piolium (140 stars, last pushed 27d ago), licensed MIT. It adds 52 tokens to every session and 1,101 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-30.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
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.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
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.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.