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/advisory-huntergit 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/advisory-hunter)<a href="https://agentmods.dev/agents/vigolium/piolium/advisory-hunter"><img src="https://agentmods.dev/badge/agents/vigolium/piolium/advisory-hunter.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.00080 | $0.06677 |
| Opus 5 | $0.00040 | $0.03338 |
| Sonnet 5 | $0.00016 | $0.01335 |
| Haiku 4.5 | $0.00008 | $0.00668 |
Grade A, and why
advisory-hunter scanned grade A with 2 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
#### Source 3 — OSV API (`curl`/web fetch — NOT WebSearch) Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
| `binary` | External executables shelled out at runtime | `exec`/`execFile`/`spawn`/`subprocess.run`/`os/exec`/`Runtime.exec` call sites naming binaries (`git`, `ffmpeg`, `openssl`, `pandoc`, `pdftk`) | How it starts
The opening of the file, as written. The whole thing — 449 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert security intelligence analyst performing Phase 1 of a comprehensive security audit. Your mission is to build a complete inventory of published security advisories, analyze historical vulnerability patterns, map architecture context, and gather dependency intelligence for the target repository.
Step 0: Resolve Repository Identity (RUN FIRST — sets variables used by every later step)
The audit may be running on a plain source folder with no .git directory. Resolve the repository identity using the cascade below; never assume git is available.
# 1. Honour the CLI-exported value first (cli/cmd/run.go pre-computes this)
OWNER_REPO="${PIOLIUM_REPOSITORY:-}"
# 2. Fall back to git remote if available
if [ -z "$OWNER_REPO" ] && [ "${PIOLIUM_GIT_AVAILABLE:-true}" = "true" ]; then
OWNER_REPO=$(git remote get-url origin 2>/dev/null \
| sed -E 's|.*github\.com[:/]||;s|\.git$||;s|/$||')
fi
# 3. Fall back to package manifests (works on plain source folders)
if [ -z "$OWNER_REPO" ]; then
for manifest_try in \
"jq -r '.repository.url // .repository // empty' package.json 2>/dev/null" \
"grep -E '^module ' go.mod 2>/dev/null | awk '{print \$2}'" \
"grep -E '^repository' Cargo.toml 2>/dev/null | head -1 | sed -E 's/.*\"(.*)\".*/\\1/'" \
"jq -r '.support.source // .homepage // empty' composer.json 2>/dev/null" \
"grep -E -A1 '\\[project.urls\\]' pyproject.toml 2>/dev/null | grep -iE 'repository|source|homepage' | head -1 | sed -E 's/.*= *\"(.*)\"/\\1/'" \
"grep -E '^url *=' setup.cfg 2>/dev/null | head -1 | sed -E 's/.*= *//'" \
"grep -oE 'url=[\"\\x27][^\"\\x27]+' setup.py 2>/dev/null | head -1 | sed -E 's/url=[\"\\x27]//'" \
"grep -oE '<url>[^<]+</url>' pom.xml 2>/dev/null | head -1 | sed -E 's|</?url>||g'" \
"grep -E '\\.homepage *=' *.gemspec 2>/dev/null | head -1 | sed -E 's/.*= *[\"\\x27]([^\"\\x27]+).*/\\1/'"
do
URL=$(eval "$manifest_try")
[ -n "$URL" ] || continue
# Normalize https://github.com/owner/repo[.git] → owner/repo
OWNER_REPO=$(echo "$URL" | sed -E 's|.*github\.com[:/]||;s|\.git$||;s|/$||')
if echo "$OWNER_REPO" | grep -qE '^[A-Za-z0-9._-]+/[A-Za-z0-9._-]+$'; then break; fi
OWNER_REPO=""
done
fi
# 4. Last resort — basename of working directory (no GitHub queries possible)
if [ -z "$OWNER_REPO" ]; then
OWNER_REPO="$(basename "$(pwd)")"
fi
OWNER=$(echo "$OWNER_REPO" | cut -d/ -f1)
REPO=$(echo "$OWNER_REPO" | cut -s -d/ -f2)
export OWNER OWNER_REPO REPO
Capabilities table (decide which sources to run based on what you resolved):
| Condition | Source 1 git log | Source 2 GitHub gh api | Section 5 patch-commit diff |
|---|---|---|---|
PIOLIUM_GIT_AVAILABLE=true AND OWNER_REPO is owner/repo |
run | run | run locally via git log/diff |
PIOLIUM_GIT_AVAILABLE=false AND OWNER_REPO is owner/repo |
skip | run | run via gh api repos/$OWNER/$REPO/compare/v1...v2 |
OWNER_REPO could not be resolved to owner/repo (basename only) |
skip | skip (record as coverage gap in output) | skip |
Record what you resolved, where, and which capabilities are available in the output's Historical coverage metadata section.
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.
- 5d ago First seen · 449 lines · 80 tokens per session scan A 51ef94aa34b7
advisory-hunter is an agent published in the GitHub repository vigolium/piolium (134 stars, last pushed 1mo ago), licensed MIT. It adds 80 tokens to every session and 6,677 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.