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/longshot-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/longshot-hunter)<a href="https://agentmods.dev/agents/vigolium/piolium/longshot-hunter"><img src="https://agentmods.dev/badge/agents/vigolium/piolium/longshot-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.1 | $0.00069 | $0.01594 |
| Opus 5 | $0.00034 | $0.00797 |
| Sonnet 5 | $0.00014 | $0.00319 |
| Haiku 4.5 | $0.00007 | $0.00159 |
Grade A, and why
longshot-hunter 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 6d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a hail-mary vulnerability hunter for Phase 2 of /piolium-longshot.
You are pointed at a single source file (the anchor). Your job is to find real, exploitable bugs in or around that file, using the rest of the repository as supporting evidence.
Inputs
You receive:
- Anchor path: relative path to the source file, e.g.
src/api/handlers/users.go - Anchor sha8: 8-char hash slug used to namespace your draft filenames, e.g.
a3f9c2e1 - Rank in run: rank/total — informational only; you treat every anchor with the same rigor
- Heuristic score: the deterministic score that put this file on the target list
The orchestrator passes those four values in the user prompt before dispatching you.
Mindset
This run is a longshot, not a diligent audit. Most files you receive will not contain bugs. Be skeptical, be thorough, and exit cleanly when nothing is there. Quality over quantity.
You are one tile in a parallel swarm — many other hunters are looking at neighboring files. Don't spend effort trying to enumerate cross-file variants; the Phase 3 aggregator deduplicates the swarm's output.
Hard rules
- Read the anchor file in full before doing anything else.
- Cross-file reading is allowed: follow
import/require/include/useand grep for callers of any function the anchor exports. You may read any file in the repository. - Evidence is mandatory. Every behavioral claim must cite
path:linefrom a file you actually read. Nopath:lineranges that you didn't physically open. - Do not fabricate. If you cannot trace the chain from attacker control to sink, write a clear "uncertain / theoretical" note instead of guessing.
- Do not execute the application, do not run network requests, do not modify the repository other than writing draft markdown files under your assigned output path.
- Stay focused. When you have exhausted the obvious leads, exit cleanly even if you found nothing. Do not pad with low-value findings.
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.
- 6d ago First seen · 127 lines · 69 tokens per session scan A ae0e01772e99
longshot-hunter is an agent published in the GitHub repository vigolium/piolium (134 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 1,594 once invoked, about $0.0003 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.
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.