scanner

A code-scanning agent that searches live Rust, TypeScript, or JavaScript files for known software hazards. A hazard taxonomy is a named set of recurring problem patterns.

In plain words
What is it for?
Running a full or focused scan, such as checking one hazard category, and returning candidate findings with file locations, matching lines, and search patterns.
Why use it?
It narrows the search to files identified as active and applies language-specific checks, making findings easier to review.

Agent

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.

agentmods
npx agentmods add agents/orin-dx/agent-plugins/scanner
Clone the repo
git clone --depth 1 https://github.com/orin-dx/agent-plugins
Per session 189 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,065 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00189 $0.01065
Opus 5 $0.00095 $0.00532
Sonnet 5 $0.00038 $0.00213
Haiku 4.5 $0.00019 $0.00106

Measured yesterday against content hash 582a68cf936a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

scanner 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 yesterday.

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.

plugins/ranger/agents/scanner.md · 61 lines

How it starts

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

<load_first> Full scan (no hazard focus category given): load both rust-hazards.md and rust-hazards-t7-t10.md (Rust), or both typescript-hazards.md and typescript-hazards-t7-t10.md (TypeScript/JavaScript) — the taxonomy set is split across the two files. Focused scan (caller supplied a specific hazard focus category): load only the file containing that taxonomy — rust-hazards-t7-t10.md/typescript-hazards-t7-t10.md for T7 or T10, otherwise the main hazards file. Language is declared in the recon manifest under the "language" field. </load_first>

Return a flat JSON array of candidate@1 entries conforming to shared/schemas/[email protected]:

[
  {
    "id": "string",
    "file": "string",
    "line": 0,
    "taxonomy": "string (T1-T10 category label)",
    "excerpt": "string (the matched line and immediate context)",
    "grep_pattern": "string"
  }
]

WHEN a caller provides a specific hazard focus category, THE SYSTEM SHALL scan only that taxonomy's patterns.

WHEN the live_files list contains more than 200 files, THE SYSTEM SHALL write candidate@1 entries to an external file after each batch of 50 files rather than accumulating all candidates in context before writing.

THE SYSTEM SHALL NEVER filter out a match based on surrounding context — emit every match and let adversary evaluate it.

THE SYSTEM SHALL NEVER scan files listed in dead_files.

Read the full file on GitHub · 61 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. yesterday First seen · 61 lines · 189 tokens per session scan A 582a68cf936a

Subscribe to this mod's changes

scanner is an agent published in the GitHub repository orin-dx/agent-plugins (1 stars, last pushed 5d ago), licensed MIT. It adds 189 tokens to every session and 1,065 once invoked, about $0.0009 per session on Opus 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.

Related

Other agents, from other repositories

security-auditor

Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.

addyosmani/agent-skills · 35 tokens

codemap

Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…

alvinunreal/oh-my-opencode-slim · 0 tokens

ring:qa

Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.

LerianStudio/ring · 52 tokens

lead

Workflow orchestrator. Use for 5-phase TDD coordination, approval gate enforcement, cross-agent task assignment, and phase transitions.

nguyenthienthanh/aura-frog · 28 tokens

replanner

Triggered by failure-classifier on F2-F4 escalations. Proposes plan-tree mutations: re-decompose stories, mark tasks discarded, re-prioritize children, or promote a node up a tier. Read-only on code; mutations applied via master-planner.

nguyenthienthanh/aura-frog · 57 tokens

geo-schema-render

Evaluates schema graph connectivity, SSR rendering of structured data, and freshness signals for GEO readiness.

greglas75/zuvo · 23 tokens