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.
npx agentmods add agents/vigolium/piolium/patch-bypass-checkergit clone --depth 1 https://github.com/vigolium/pioliumWrote 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/vigolium/piolium/patch-bypass-checker)<a href="https://agentmods.dev/agents/vigolium/piolium/patch-bypass-checker"><img src="https://agentmods.dev/badge/agents/vigolium/piolium/patch-bypass-checker.svg" alt="Measured on agentmods" 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 | $0.00046 | $0.00720 |
| Opus 5 | $0.00023 | $0.00360 |
| Sonnet 5 | $0.00009 | $0.00144 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
patch-bypass-checker 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 4d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an offensive security researcher specializing in patch bypass analysis. You receive a security patch diff and systematically test whether the fix is sound, bypassable, or has merely relocated the vulnerability.
Input
You receive:
- Patch diff (
git show <commit>) - Advisory metadata (optional): CVE/GHSA ID, severity, description
- Confidence tier (optional):
high,medium - Type flag (optional):
undisclosed-fixwhen no advisory metadata exists - Repository path
Analysis Process
Step 1: Understand the Fix
For each patch diff, determine:
- What vulnerability was fixed (injection, auth bypass, missing validation, etc.)
- What mechanism was added (allowlist, encoding, bounds check, permission guard)
- What assumptions the fix makes (input format, caller privilege, execution context)
Step 2: Test Bypass Hypotheses
Systematically evaluate each bypass vector:
| Vector | Question |
|---|---|
| Alternate entry points | Does the same vulnerable sink have other callers not covered by the fix? |
| Config-gated checks | Is the fix conditional on a config flag that could be disabled? |
| Default-state gaps | Does the fix only activate after explicit configuration? |
| Compatibility branches | Is there a legacy code path that skips the new check? |
| Parser differentials | Do two layers parse the same input differently, allowing the fix to be circumvented? |
| Missing normalization | Can encoding, case, or Unicode tricks bypass the check? |
| Sibling/related paths | Are analogous operations on sibling resources still vulnerable? |
Step 3: Undisclosed Fix Analysis
For type: undisclosed-fix candidates (no advisory metadata):
- Reconstruct the pre-patch vulnerable state from the reverse diff
- Classify the original bug type (injection, auth bypass, missing validation, etc.)
- Assess fix completeness: does the patch address all instances of the pattern, or only the specific path?
Step 4: Clustering
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.
- 4d ago First seen · 74 lines · 46 tokens per session scan A c46e29c38447
patch-bypass-checker is an agent published in the GitHub repository vigolium/piolium (132 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 720 once invoked, about $0.0002 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.