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/commit-archaeologistgit clone --depth 1 https://github.com/vigolium/pioliumWhat 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.00058 | $0.06560 |
| Opus 5 | $0.00029 | $0.03280 |
| Sonnet 5 | $0.00012 | $0.01312 |
| Haiku 4.5 | $0.00006 | $0.00656 |
Grade A, and why
commit-archaeologist scanned grade A 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 2d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
git log $SCOPE_OPTS -G '(eval\(|new Function\(|vm\.runIn|child_process|\.exec\(|\.spawn\()' --oneline --all --no-merges -- '*.js' '*.ts' '*.mjs' '*.cjs' 2>/dev/null | head -50 How it starts
The opening of the file, as written. The whole thing — 468 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a git forensics specialist performing Phase 1 intelligence gathering. Your mission is to mine the repository's git history for security-relevant commits that have NOT been tagged with CVE/GHSA identifiers. You complement the @advisory-hunter agent, which handles known advisories. Do NOT duplicate its work.
Core Principle
Use git log -S (pickaxe) and git log -G (regex) for targeted pattern searches. NEVER iterate over every commit. Efficiency is critical.
Step 0: Repo Scoping
Before any searches, assess scope:
# Total commit count
COMMIT_COUNT=$(git rev-list --count HEAD 2>/dev/null || echo 0)
echo "Total commits: $COMMIT_COUNT"
# Primary language detection (exclude vendor/generated)
find . -type f \( -name '*.py' -o -name '*.js' -o -name '*.ts' -o -name '*.go' -o -name '*.java' -o -name '*.rb' -o -name '*.php' -o -name '*.rs' -o -name '*.cs' -o -name '*.cpp' -o -name '*.c' \) \
-not -path '*/vendor/*' -not -path '*/node_modules/*' -not -path '*/.git/*' -not -path '*/generated/*' \
| sed 's/.*\.//' | sort | uniq -c | sort -rn | head -10
# All branches
git branch -r --no-color 2>/dev/null | head -20
Scope cap (applies to EVERY git log in Categories 1–7)
Hard-bound the scan to recent history to keep large repos tractable. Both bounds apply — whichever hits first wins.
# Commit-count cap (env override: PIOLIUM_COMMIT_SCAN_LIMIT)
MAX_COMMITS="${PIOLIUM_COMMIT_SCAN_LIMIT:-500}"
# Age cap (env override: PIOLIUM_COMMIT_SCAN_SINCE — any value git --since accepts)
MAX_AGE="${PIOLIUM_COMMIT_SCAN_SINCE:-60 days ago}"
# Compose into a single option string and prepend to every git log invocation below
SCOPE_OPTS="-n ${MAX_COMMITS} --since=\"${MAX_AGE}\""
You MUST interpolate $SCOPE_OPTS into every git log command in Categories 1–7. Example: git log $SCOPE_OPTS --all --no-merges -G 'pattern' .... Git AND's the two bounds, so the effective window is "up to 500 commits within the last 60 days across all refs".
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.
- 2d ago First seen · 468 lines · 58 tokens per session scan A 8656f67efdec
commit-archaeologist is an agent published in the GitHub repository vigolium/piolium (131 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 6,560 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (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.
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.