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/pollyglot/google-play-cli/issue-trackergit clone --depth 1 https://github.com/PollyGlot/google-play-cliWhat 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.00736 |
| Opus 5 | $0.00000 | $0.00368 |
| Sonnet 5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00074 |
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 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.
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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue tracker: GitHub
Issues et PRDs vivent dans GitHub Issues sur PollyGlot/google-play-cli.
Utiliser le CLI gh pour toute opération.
Conventions de base
- Créer une issue :
gh issue create --title "..." --body "$(cat <<'EOF' ... EOF)" - Lire une issue :
gh issue view <n> --comments - Lister :
gh issue list --state open --json number,title,labels,body - Commenter :
gh issue comment <n> --body "..." - Labels :
gh issue edit <n> --add-label "..."/--remove-label "..." - Fermer :
gh issue close <n> --comment "..."
Taxonomie d'issue locale (lire avant tout)
Quatre types d'issue cohabitent. Ils se distinguent par un label type:*
et une convention de titre. Voir docs/ROADMAP.md pour la
vue d'ensemble du projet.
| Type | Label | Convention de titre |
|---|---|---|
| PRD | type:prd |
PRD: <area> ou PRD — <area> |
| Slice | type:slice |
libre (souvent préfixé par l'area, ex: Apps: ...) |
| Arch | type:arch |
[arch] ... |
| Parking | type:parking |
Parking: ... |
Chaque issue doit aussi porter un area:* (area:auth, area:apps,
area:releases, area:tracks, area:reviews) et une priority:*
(priority:high/priority:medium/priority:low).
Quand un skill dit "publish to the issue tracker"
Créer une issue GitHub. Appliquer les labels appropriés :
/to-prd→ ajoutetype:prd+ le bonarea:*+ready-for-agent./to-issues→ chaque slice publiée portetype:slice+area:*+ready-for-agent. Référencer le PRD parent dans le body via## Parentpointant vers#<num>du PRD. Mettre à jour le body du PRD pour ajouter une section "Implementation issues" avec la checklist- [ ] #N./triage→ applique le label d'état (needs-triage,needs-info,ready-for-agent,ready-for-human,wontfix) selon le résultat.
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 · 58 lines · 0 tokens per session scan A 8391d73e06f5
issue-tracker is an agent published in the GitHub repository PollyGlot/google-play-cli (5 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 736 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-31.
Other agents, from other repositories
issue-tracker
Predict issues and PRDs live in Consensys Jira.
tech-manager
Use to stand up the dev pod, plan sprints, assign work in parallel, run standups, unblock ICs, and track progress. The orchestration layer between executives and ICs. Owns the sprint plan, the kanban board, and the daily report. Spawns parallel dev agents and the code-reviewer; escalates blockers to tech-lead or CTO.
issue-tracker
Issues and PRDs for launch-store live as GitHub issues on YosefHayim/launch-store. Use the gh CLI for all operations - it infers the repo from git remote -v automatically inside a clone.
ceo
Use as the top-level orchestrator at the start of any new app project, or when the user wants strategic direction, scope decisions, prioritization tradeoffs, or a go/no-go call on a feature. Owns vision, success metrics, and final scope. Delegates product depth to CPO and engineering depth to CTO.
chief-of-staff
Use as the single founder interface — prepares decision briefs, tracks unresolved commitments, ensures every founder decision reaches a specification, and maintains docs/17-founder-inbox.md. Exists to reduce founder load, so it is only worth running if it removes more decisions than it creates.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker (GitHub Issues — see issue-tracker.md).