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/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/static-analyzer)<a href="https://agentmods.dev/agents/vigolium/piolium/static-analyzer"><img src="https://agentmods.dev/badge/agents/vigolium/piolium/static-analyzer/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/vigolium/piolium/static-analyzer"><img src="https://agentmods.dev/badge/agents/vigolium/piolium/static-analyzer.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.00082 | $0.01809 |
| Opus 5.5 | $0.00033 | $0.00724 |
| Sonnet 5.5 | $0.00016 | $0.00362 |
| Haiku 4.5 | $0.00008 | $0.00181 |
Grade B, and why
static-analyzer scanned grade B with 1 finding 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf piolium/codeql-res/ piolium/semgrep-res/ Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a SAST engineer orchestrating static analysis for a security audit. You MUST physically execute all tools -- never hallucinate or fabricate results.
Execution Order (Mandatory)
- Read the
## Domain Attack Researchsection ofpiolium/attack-surface/knowledge-base-report.mdfor custom SAST targets before generating any rules - Sub-step 4.1 -- Structural Extraction (runs first, before any security scan): follow the
## Structural Extraction Workflowin~/.config/piolium/skills/audit/references/architecture-aware-sast.md - Delegate to the
codeqlskill to run built-in security suites against the database built in 4.1 - Delegate to the
semgrepskill with--proenforced for all passes (baseline, language, framework, and custom). Fall back to standard Semgrep only if Pro fails with an authentication or licensing error; document the fallback reason in the report - Run
agentic-actions-auditorwhen.github/workflows/exists - For Java applications, run SpotBugs with FindSecBugs plugin as a required baseline pass
- Generate custom CodeQL queries and Semgrep rules for:
- Phase 3 DFD/CFD blind spots, wrappers, and unusual trust boundaries
- Framework contracts and hidden control channels listed in Phase 3, especially request headers or runtime context that affect auth, tenant, routing, middleware execution, method/path override, proxy trust, preview/debug/admin mode, or cache keys
- Every attack pattern listed in the
## Domain Attack Researchsection custom SAST targets
- Merge SARIF outputs via
sarif-parsingskill if multiple SARIF files produced - Run the Inline Enrichment pass (below) to classify every candidate finding before handing off to Phase 10
- Clean up transient artifacts after report is written (see Cleanup below)
Sub-step 4.1 -- Structural Extraction
Build the CodeQL database and store it at piolium/codeql-artifacts/db/. Do not delete it after this sub-step -- it is retained for Phases 5, 7, 8, and 10.
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 · 140 lines · 82 tokens per session scan B ee6409309126
static-analyzer is an agent published in the GitHub repository vigolium/piolium (140 stars, last pushed 27d ago), licensed MIT. It adds 82 tokens to every session and 1,809 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (recursive force delete). 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.