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/triage-labelsgit clone --depth 1 https://github.com/PollyGlot/google-play-cliWrote 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/pollyglot/google-play-cli/triage-labels)<a href="https://agentmods.dev/agents/pollyglot/google-play-cli/triage-labels"><img src="https://agentmods.dev/badge/agents/pollyglot/google-play-cli/triage-labels.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.00553 |
| Opus 5 | $0.00000 | $0.00277 |
| Sonnet 5 | $0.00000 | $0.00111 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
triage-labels 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage labels
Les skills parlent en termes de cinq rôles canoniques de triage. Cette table mappe ces rôles vers les labels réels du tracker.
Rôles d'état (un seul par issue)
| Rôle canonique | Label dans ce repo | Signification |
|---|---|---|
needs-triage |
needs-triage |
Maintainer doit évaluer |
needs-info |
needs-info |
En attente d'info du reporter |
ready-for-agent |
ready-for-agent |
Fully specified, prêt pour un agent AFK |
ready-for-human |
(pas encore créé) | Demande implémentation humaine — créer à la demande |
wontfix |
wontfix |
Ne sera pas actionné |
Rôles de catégorie (un seul par issue)
| Rôle canonique | Label dans ce repo |
|---|---|
bug |
bug |
enhancement |
enhancement |
Labels de type d'issue (un seul par issue — local à ce projet)
Au-delà des rôles canoniques, ce projet maintient une taxonomie par type d'issue pour distinguer PRDs, slices, refacto d'archi et parking. Voir issue-tracker.md pour les conventions complètes.
| Label | Quand l'appliquer |
|---|---|
type:prd |
PRD produit par /to-prd ou ses équivalents |
type:slice |
Sous-issue d'un PRD, produite par /to-issues |
type:arch |
Refacto / décision d'archi isolée (titre [arch] ...) |
type:parking |
Idée gardée hors MVP (titre Parking: ...) |
Labels d'area (un seul par issue)
area:auth, area:apps, area:releases, area:tracks, area:reviews.
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 · 49 lines · 0 tokens per session scan A de6d206e36bf
triage-labels is an agent published in the GitHub repository PollyGlot/google-play-cli (5 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 553 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
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.
release-manager
Use when the sprint is done and the team wants to prepare a release — assembles a signed, submission-ready build for iOS and Android, owns version bumps, build numbers, release notes, and the submission checklist. You never upload or submit to a store — that is always the human founder's action. Triggered by /app-ship…
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.
product-validator
Use before scope-lock, and again whenever the PRD or the backlog changes materially, to check the derived product documents against the founder's own recorded words. Compares docs/00-founder-intent/ to docs/10-prd.md and flags omitted intent, invented requirements, silent scope change, acceptance criteria that do not…
cpo
Use after the CEO has set vision, or whenever the project needs product depth — PRD, user stories, acceptance criteria, prioritization, scope cuts, feature tradeoffs, or stakeholder communication. Owns the PRD and the product backlog. Delegates information architecture and flows to ux-architect, screen composition to…
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).