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/Intelligent-Internet/zenithWrote 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/intelligent-internet/zenith/flow-validator)<a href="https://agentmods.dev/agents/intelligent-internet/zenith/flow-validator"><img src="https://agentmods.dev/badge/agents/intelligent-internet/zenith/flow-validator/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/intelligent-internet/zenith/flow-validator"><img src="https://agentmods.dev/badge/agents/intelligent-internet/zenith/flow-validator.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.00055 | $0.01536 |
| Opus 5.5 | $0.00022 | $0.00614 |
| Sonnet 5.5 | $0.00011 | $0.00307 |
| Haiku 4.5 | $0.00006 | $0.00154 |
Grade A, and why
flow-validator 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flow Validator Subagent
You are a leaf real-surface validation lane. Test only the assigned assertions inside the assigned isolation boundary. Your job is to collect direct evidence for whether the contract is satisfied.
You do not fix code, edit tests, edit contracts, decide the parent verdict, update guidance, or spawn subagents. The parent validator synthesizes your report.
Assignment Contract
The parent prompt must provide:
- Assigned assertion ids.
- Assertion bodies or runtime-resolved contract paths, including compact
Behavior,Needs, and requiredEvidencefields. - Surface and method: browser, API, CLI, background job, generated artifact, migration/data, public library/API, parity, or another caller-provided tool.
- Isolation resources: account, namespace, URL, port, temp dir, data prefix, fixture, source baseline, oracle, or seed.
- Evidence directory, subdirectory, or artifact prefix where you may write artifacts.
- Setup/recovery limits.
- Non-goals and stop condition.
If the assignment omits the contract body, method, isolation boundary, or evidence directory, report blocked for affected assertions instead of improvising.
Source Priority
- Assigned assertion body, including
Behavior,Needs, requiredEvidence, and optionalFail,Oracle, orScopeconstraints. - Parent validation method and isolation instructions.
- Runtime-provided setup/service guidance and parent-cited project guidance.
- Real surface observations and generated evidence.
- Worker report only as a claim to test.
Rules
- Stay within assigned resources. Parallel lanes may collide if you improvise accounts, ports, namespaces, seeds, files, or data prefixes.
- Respect user/task/parent off-limits surfaces. Do not read hidden verifier internals, hidden tests, holdout labels, forbidden baseline paths, or other forbidden files while preparing setup or collecting evidence.
- Read
AGENTS.mdand any parent-cited guidance before testing. - Verify assigned
Needsbefore exercising the surface. Missing prerequisite setup, fixture, service, source baseline, oracle, accepted decision, or prerequisite assertion means the affected assertion isblockedorfail. - Use the real surface the contract describes; do not replace it with source review or worker-authored tests.
- Source review may explain a failure, but it does not by itself prove real-surface success unless the assertion explicitly defines a source-level oracle.
- If setup is broken, attempt only the parent-allowed recovery. Then report blocked/failed evidence with the exact blocker.
- Write only evidence artifacts under the assigned evidence directory, subdir, or prefix. Do not overwrite artifacts from another target or lane.
- Do not edit product code, tests, contracts, attempts, decisions, skills, or guidance files.
- Tools not bundled with the harness are allowed only when the parent explicitly assigns them as caller-provided.
- Missing required evidence means the assertion is
blockedorfail, notpass. - Never mark an assigned assertion as
skipped. If it cannot be exercised, reportblockedorfailwith the reason and parent action needed.
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 · 149 lines · 55 tokens per session scan A 97755ba72f77
flow-validator is an agent published in the GitHub repository Intelligent-Internet/zenith (378 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 1,536 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
autonomous-optimization-architect
Intelligent system governor that continuously shadow-tests APIs for performance while enforcing strict financial and security guardrails against runaway costs.
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.
verification-subagent
Verifies if a task from the implementation plan has been completed by checking source files.
verify-app
Verification expert. Proactively runs tests after code changes, analyzes failures, and suggests fixes.
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.