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/tgyd-helige/pi/issue-trackergit clone --depth 1 https://github.com/TGYD-helige/piWrote 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/tgyd-helige/pi/issue-tracker)<a href="https://agentmods.dev/agents/tgyd-helige/pi/issue-tracker"><img src="https://agentmods.dev/badge/agents/tgyd-helige/pi/issue-tracker.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.00000 | $0.00092 |
| Opus 5 | $0.00000 | $0.00046 |
| Sonnet 5 | $0.00000 | $0.00018 |
| Haiku 4.5 | $0.00000 | $0.00009 |
Grade A, and why
issue-tracker 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 3d 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.
What it actually says
Issue Tracker
This repository uses GitHub Issues.
For code reviews, the pull request title and body are the primary specification. Issues referenced with
Closes #N, Fixes #N, or Resolves #N are additional specification inputs. The automated Pi reviewer
receives those inputs from the trusted workflow and must not fetch or execute pull request content itself.
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.
- 3d ago First seen · 8 lines · 0 tokens per session scan A f33c59c4d11e
issue-tracker is an agent published in the GitHub repository TGYD-helige/pi (54 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 92 tokens. 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
Breaker
Ruthless QA tester for ScreenHand. Finds bugs in the 6-layer desktop automation platform. Measured by bugs found, not tests passed.
Builder
Senior developer for ScreenHand. Ships clean TypeScript that survives Breaker and Ghost. Knows the 6-layer architecture, strict tsconfig, and all 111 MCP tools.
Chaos
Chaos engineer for ScreenHand. Injects simultaneous failures, exhausts resources, corrupts state mid-operation, and verifies recovery. Tests what happens when 3 things break at once under load.
Chief
Engineering manager for ScreenHand. Knows the 6-layer architecture, implementation plan, and website redesign. Rates team by real output — bugs found, vulns caught, code shipped. No participation trophies.
Ghost
Offensive security hacker for ScreenHand. Finds exploits in the desktop automation platform — process spawning, path traversal, injection, supply chain. No ethical hesitation on authorized targets.
Outsider
Real user simulator for ScreenHand. Two modes — technical (developer integrating MCP tools) and non-technical (someone installing the plugin). Finds UX issues devs are blind to.