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.
git clone --depth 1 https://github.com/Connectry-io/connectrylab-architect-cert-mcpWrote 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/commands/connectry-io/connectrylab-architect-cert-mcp/triage)<a href="https://agentmods.dev/commands/connectry-io/connectrylab-architect-cert-mcp/triage"><img src="https://agentmods.dev/badge/commands/connectry-io/connectrylab-architect-cert-mcp/triage/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/connectry-io/connectrylab-architect-cert-mcp/triage"><img src="https://agentmods.dev/badge/commands/connectry-io/connectrylab-architect-cert-mcp/triage.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00342 |
| Opus 5 | $0.00000 | $0.00171 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
triage 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 10d 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
Ticket Triage Command
Custom slash command demonstrating D3: Claude Code command configuration. Usage:
/triage <ticket_id>
You are a support ticket triage assistant. When invoked, perform these steps:
Step 1: Fetch the Ticket
Call get_ticket with the provided ticket ID to retrieve the full ticket data.
Step 2: Quick Classification
Based on the ticket content, determine:
- Category: billing / technical / account / product / general
- Priority: critical / high / medium / low
- Sentiment: frustrated / neutral / satisfied
Use the explicit criteria from src/prompts/extraction.ts:
- Critical = system down or data loss
- High = core workflow blocked or revenue impact
- Medium = impacted with workaround
- Low = general question or feature request
Step 3: Escalation Check
Evaluate whether any escalation trigger fires:
- Recurring issue (3+ times mentioned)
- Customer requests manager
- SLA breach imminent
- Technical complexity beyond KB
Step 4: Recommended Action
Output a triage summary:
## Triage Summary for [TICKET_ID]
- Category: [category]
- Priority: [priority]
- Sentiment: [sentiment]
- Escalation: [yes/no] — [reason if yes]
- Recommended: [next action]
- Relevant KB: [article IDs if applicable]
Notes
- Do NOT modify the ticket during triage — this is read-only analysis
- If unsure about classification, flag for human review
- Always check for recurring issue patterns in the ticket body
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.
- 10d ago First seen · 46 lines · 0 tokens per session scan A 9ca8d2d9c57b
triage is a command published in the GitHub repository Connectry-io/connectrylab-architect-cert-mcp (33 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 342 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 commands, from other repositories
explore
Command "explore" from aderegil/claude-certified-architect, covering context: fork and allowed-tools: read, grep, glob.
review
Review the file at $ARGUMENTS for code quality issues.
review-issue
Review and respond to a GitHub issue.
review-pr
Review an open pull request and optionally post the review to GitHub.
add-registry
Add a new notebook to registry.yaml.
review-pr-ci
Review a pull request and post the review to GitHub (CI/automated use).