build-verifier

build-verifier is an agent for Claude Code from zerx-lab/FluxDown. It costs 48 tokens per session (522 once invoked), scanned A, original, AGPL-3.0.

A read-only checker for a specified software crate or subproject. A crate is a Rust package or component that can be built and tested separately.

In plain words
What is it for?
Use it after multi-file changes to run the build, lint, and targeted tests for a chosen crate or subproject.
Why use it?
It provides a final check without changing the files being reviewed. The summary shows whether compilation, lint checks, and focused tests pass.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit Use it after multi-file changes to run the build, lint, and targeted tests for a chosen crate or subproject.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/zerx-lab/fluxdown/build-verifier
About the project

FluxDown is a free, open-source download manager built with Rust that handles web downloads, FTP, BitTorrent, eD2K, and HLS or DASH streams. It is for people who want resumable, browser-integrated downloads with a local desktop interface, and its built-in MCP server lets AI clients manage those downloads.

zerx-lab/FluxDown · 5,039 stars · on GitHub · fluxdown.com

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/zerx-lab/FluxDown

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 build-verifier

README.md
[![agentmods](https://agentmods.dev/badge/agents/zerx-lab/fluxdown/build-verifier/github.svg)](https://agentmods.dev/agents/zerx-lab/fluxdown/build-verifier)
Your own site
<a href="https://agentmods.dev/agents/zerx-lab/fluxdown/build-verifier"><img src="https://agentmods.dev/badge/agents/zerx-lab/fluxdown/build-verifier/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 build-verifier

Your own site · 80×15
<a href="https://agentmods.dev/agents/zerx-lab/fluxdown/build-verifier"><img src="https://agentmods.dev/badge/agents/zerx-lab/fluxdown/build-verifier.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 522 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown 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.00048 $0.00522
Opus 5.5 $0.00019 $0.00209
Sonnet 5.5 $0.00010 $0.00104
Haiku 4.5 $0.00005 $0.00052

Measured 2d ago against content hash 35b39f5e9607, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

build-verifier 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 2d 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.

.omp/agents/build-verifier.md · 23 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 2d ago Changed 35b39f5e9607
  2. 3d ago Changed · +1 lines 150811607f01
  3. 8d ago Changed 4b578ee97f6f
  4. 13d ago Changed 0c53ce82f0d2
  5. 16d ago Changed 5e860d8c67ab
  6. 26d ago Changed da2ab9af4605
  7. 1mo ago First seen · 22 lines · 48 tokens per session scan A ed0d0a021c35

Subscribe to this mod's changes

build-verifier is an agent published in the GitHub repository zerx-lab/FluxDown (5,039 stars, last pushed today), licensed AGPL-3.0. It adds 48 tokens to every session and 522 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.

Related

Other agents, from other repositories

rust-testing-engineer

Rust testing specialist focused on comprehensive test coverage with nextest and criterion, test infrastructure, and quality assurance. Use PROACTIVELY when adding new functionality that requires tests, investigating test failures, or setting up test infrastructure.

bug-ops/zeph · 49 tokens

rust-implementer

Rust TDD implementer worker. Makes a frozen failing test suite pass with the smallest idiomatic change; forbidden from modifying test files. Half of the adversarial Rust fix pair (with rust-test-author). Use when implementing Rust code against frozen tests.

vinnie357/claude-skills · 55 tokens

rust-test-author

Rust TDD test-author worker. Writes failing tests against a provided spec/acceptance criteria and freezes them on commit; forbidden from writing implementation code. Half of the adversarial Rust fix pair (with rust-implementer). Use when a Rust change needs tests authored before implementation.

vinnie357/claude-skills · 60 tokens

rust-pro

Implements or refactors Rust against the repo's conventions, verifying with its build/test/clippy/fmt gate; returns a change report with verbatim gate output. - Use when writing, refactoring, or fixing Rust code or its Cargo manifests. Spawn one per module-sized task. Not for reviewing a diff (rust-reviewer).

uwuclxdy/agenticat · 70 tokens

rust-tests-reviewer

Rust test quality review for built-in test framework patterns, assert macros, async tests, mockall, proptest, rstest, insta snapshots, criterion benchmarks, and serialtest isolation.

vladolaru/claude-code-plugins · 41 tokens

rust-pro

Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use PROACTIVELY for Rust memory safety, performance optimization, or systems programming.

NOMARJ/sigil · 49 tokens