Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/geekatron/jerrynpx agentmods add agents/geekatron/jerry/ps-investigatorWrote 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/geekatron/jerry/ps-investigator)<a href="https://agentmods.dev/agents/geekatron/jerry/ps-investigator"><img src="https://agentmods.dev/badge/agents/geekatron/jerry/ps-investigator.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.00031 | $0.04631 |
| Opus 5 | $0.00015 | $0.02315 |
| Sonnet 5 | $0.00006 | $0.00926 |
| Haiku 4.5 | $0.00003 | $0.00463 |
Grade A, and why
ps-investigator 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 507 lines · 31 tokens per session scan A 4855fc61101b
ps-investigator is an agent published in the GitHub repository geekatron/jerry (32 stars, last pushed yesterday), with no licence file. It adds 31 tokens to every session and 4,631 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-09-03.
Other agents, from other repositories
client-scanner
Scan client project structure, detect tech stack, check brana alignment. Use when entering an unfamiliar client project or for project health checks. Not for: business stage classification, knowledge recall, web research.
python-pitfall-scanner
Use this agent to find concrete correctness defects in Python code — the pitfalls that silently produce wrong results rather than raising. Covers mutable default arguments, late-binding closures in loops, unreachable except ordering, return inside finally, eq without hash, mutation during iteration, the asyncio family…
typing-integrity-auditor
Use this agent to find defects that a type checker can prove — and, more importantly, to find annotations that have silently stopped checking anything. Backed by checktyping.py, which runs mypy with the project's own config plus a labelled --disallow-any-unimported second pass. Its signature finding is the phantom…
python-general-engineer
Python development: features, debugging, code review, performance. Modern Python 3.12+ patterns.
silent-failure-hunter
PRFlow review-engine reviewer; use to hunt silent failures and weak error handling in a diff.
comment-analyzer
PRFlow review-engine reviewer; use to check code comments match the code before a PR.