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/orin-dx/agent-pluginsWrote 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/orin-dx/agent-plugins/boundary-tracer)<a href="https://agentmods.dev/agents/orin-dx/agent-plugins/boundary-tracer"><img src="https://agentmods.dev/badge/agents/orin-dx/agent-plugins/boundary-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/orin-dx/agent-plugins/boundary-tracer"><img src="https://agentmods.dev/badge/agents/orin-dx/agent-plugins/boundary-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.00038 | $0.00829 |
| Opus 5.5 | $0.00015 | $0.00332 |
| Sonnet 5.5 | $0.00008 | $0.00166 |
| Haiku 4.5 | $0.00004 | $0.00083 |
Grade A, and why
boundary-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.
What it actually says
<load_first> Load one boundary reference for the candidate language:
- Rust:
shared/references/hazards/rust-boundaries.md. - TypeScript or JavaScript:
shared/references/hazards/typescript-boundaries.md. - Python:
shared/references/hazards/python-boundaries.md. - Go:
shared/references/hazards/go-boundaries.md. </load_first>
Return a field-survival-map@1 (see shared/schemas/field-[email protected]):
{
"candidate_id": "string (from candidate@1)",
"struct_or_type": "string",
"fields": [
{
"name": "string",
"reaches_boundary": true | false | "uncertain",
"boundary_type": "network|subprocess|storage|render|none|unknown",
"evidence": "string (exact function calls, parameter names, or argument positions observed)",
"last_observed_site": "file:line"
}
],
"reasoning": "string"
}
Pass this map to adversary alongside the original candidate@1 entry.
THE SYSTEM SHALL NEVER invoke this agent for taxonomy categories other than T7 or T10.
WHEN a field trace ends at an opaque function boundary with no readable implementation, THE SYSTEM SHALL set reaches_boundary to uncertain and record the opaque call site in last_observed_site.
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 Changed · +4 lines 5414806431e2
- 1mo ago Changed · +2 lines · -159 tokens per session 13f6041d3894
- 1mo ago First seen · 62 lines · 197 tokens per session scan A fe2ed2620d23
boundary-tracer is an agent published in the GitHub repository orin-dx/agent-plugins (1 stars, last pushed 22d ago), licensed MIT. It adds 38 tokens to every session and 829 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.
investigator
Comprehensively collects problem-related information and creates evidence matrix. Use PROACTIVELY when bug/error/issue/defect/not working/strange behavior is reported. Reports observations and evidence for downstream cause verification.
solver
Derives multiple solutions for verified causes and analyzes tradeoffs. Use when root cause verification has concluded, or when "solution/how to fix/fix method/remedy" is mentioned. Focuses on solutions from given conclusions without investigation.
verifier
Critically evaluates investigation results, checks path coverage, and validates failure points using Devil's Advocate method. Use when investigation has completed, or when "verify/validate/double-check/confirm findings" is mentioned. Focuses on verification and conclusion derivation.
root-cause-debugger
Investigation specialist that finds and PROVES the root cause of a bug before any code is changed. Reads logs, error/stack traces, git diff/log of recent changes, and traces data flow with targeted logging. Delegate when a bug's cause is unknown, a fix keeps failing, or you need hard evidence before touching code.…
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.