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/openshift-eng/two-node-toolboxWrote 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/commands/openshift-eng/two-node-toolbox/data_corruption)<a href="https://agentmods.dev/commands/openshift-eng/two-node-toolbox/data_corruption"><img src="https://agentmods.dev/badge/commands/openshift-eng/two-node-toolbox/data_corruption/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/commands/openshift-eng/two-node-toolbox/data_corruption"><img src="https://agentmods.dev/badge/commands/openshift-eng/two-node-toolbox/data_corruption.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.00006 | $0.00718 |
| Opus 5.5 | $0.00002 | $0.00287 |
| Sonnet 5.5 | $0.00001 | $0.00144 |
| Haiku 4.5 | $0.00001 | $0.00072 |
Grade A, and why
data_corruption 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
etcd has built in automated data corruption detection to prevent member state from diverging.
Enabling data corruption detection
Data corruption detection can be done using:
- Initial check, enabled with
--experimental-initial-corrupt-checkflag. - Periodic check of:
- Compacted revision hash, enabled with
--experimental-compact-hash-check-enabledflag. - Latest revision hash, enabled with
--experimental-corrupt-check-timeflag.
- Compacted revision hash, enabled with
Initial check will be executed during bootstrap of etcd member. Member will compare its persistent state vs other members and exit if there is a mismatch.
Both periodic check will be executed by the cluster leader in a cluster that is already running. Leader will compare its persistent state vs other members and raise a CORRUPT ALARM if there is a mismatch. Both checks serve the same purpose, however they are both worth enabling to balance performance and time to detection.
- Compacted revision hash check - requires regular compaction, minimal performance cost, handles slow followers.
- Latest revision hash check - high performance cost, doesn't handle slow followers or frequent compactions.
Compacted revision hash check
When enabled using --experimental-compact-hash-check-enabled flag, check will be executed once every minute.
This can be adjusted using --experimental-compact-hash-check-time flag using format: 1m - every minute, 1h - evey hour.
This check extends compaction to also calculate checksum that can be compared between cluster members.
Doesn't cause additional database scan making it very cheap, but requiring a regular compaction in cluster.
Latest revision hash check
Enabled using --experimental-corrupt-check-time flag, requires providing an execution period in format: 1m - every minute, 1h - evey hour.
Recommended period is a couple of hours due to a high performance cost.
Running a check requires computing a checksum by scanning entire etcd content at given revision.
Restoring a corrupted member
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 · 72 lines · 6 tokens per session scan A 5af503e0191f
data_corruption is a command published in the GitHub repository openshift-eng/two-node-toolbox (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 6 tokens to every session and 718 once invoked, about $0.0000 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 commands, from other repositories
codesage-reset
Fully regenerate a project's CodeSage index under its writer lock, with a separate offline recovery procedure for an unreadable database.
audit-performance
Performance audit. Detects N+1 queries, memory issues, caching gaps, inefficient loops, batch processing problems, algorithm complexity, connection pools, serialization overhead.
sqlscript-validate
Validates SQLScript code for syntax, patterns, and best practices with auto-fix capability.
pg-health
Read-only PostgreSQL health check with pgbot, then a prioritized diagnosis.
data-flow-analysis
Trace how data flows through the system from input to output.
cleanup
Detect and remove orphaned code, unused components, dead routes, and stale database artifacts.