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/graphpilot-oss/graphpilot/triage-labelsgit clone --depth 1 https://github.com/graphpilot-oss/graphpilotWhat 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.00512 |
| Opus 5 | $0.00000 | $0.00256 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
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 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
| Label in mattpocock/skills | Label in our tracker | Meaning |
|---|---|---|
needs-triage |
needs-triage |
Maintainer needs to evaluate this issue |
needs-info |
needs-info |
Waiting on reporter for more information |
ready-for-agent |
ready-for-agent |
Fully specified, ready for an AFK agent |
ready-for-human |
ready-for-human |
Requires human implementation |
wontfix |
wontfix |
Will not be actioned |
When a skill mentions a role (e.g. "apply the AFK-ready triage label"), use the corresponding label string from this table.
Create any missing role label on first use with gh label create <name>.
Edit the right-hand column to match whatever vocabulary you actually use.
Severity labels
P0 / P1 / P2 mark priority independent of the triage roles above.
Connect-failure fast lane
connect-failure marks an issue where an agent client can't connect to or
start the MCP server — the highest-severity report class, since it makes the
tool look broken on first contact.
Policy:
connect-failure⇒P0, same-day human response. Don't leave a connection report sitting inneeds-triage.- The bug template (
.github/ISSUE_TEMPLATE/bug_report.md) has a "Connect/startup failure" checkbox. Checking it auto-applies bothconnect-failureandP0via.github/workflows/triage-connect-failure.yml. - The template asks reporters to paste
graphpilot doctor --json— start triage there; it usually pinpoints the cause (Node,PATH, index, handshake, or a missing client config entry). - Self-serve fixes live in
docs/troubleshooting.md; link reporters there while you investigate.
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 · 42 lines · 0 tokens per session scan A fb398f7faadb
triage-labels is an agent published in the GitHub repository graphpilot-oss/graphpilot (15 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 512 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
mcp-connection
Connect Claude Code or any MCP-compatible agent to your Projektor instance.
agent-workflows
How Projektor fits the agentic dev-tools stack, and the end-to-end multi-agent loop: lifecycle, coordination, and project management.
tool-catalog
Every MCP tool Projektor exposes, generated from source.
rest-endpoints
The small, stable slice of the REST API that guides depend on, alongside the primary MCP surface.
workflow-spec
The canonical agent workflow rules: definition of ready, state machine, human gates, WIP limits.
flow-metrics
Every metric getflowmetrics returns, what it measures, and how to read it.