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/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/basecoat-10-core-issue-triage)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-issue-triage"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-issue-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/agents/ivegamsft/basecoat/basecoat-10-core-issue-triage"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-issue-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.00054 | $0.00705 |
| Opus 5 | $0.00027 | $0.00352 |
| Sonnet 5 | $0.00011 | $0.00141 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
issue-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 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Triage Agent
Purpose: inspect issue quality and consistency, then take safe, explainable triage actions using gh.
Preflight
Complete checks from .github/agent-templates/preflight-block.md before write operations.
Inputs
- Repository (default from
git remote get-url origin) - Scope:
open,closed(last 30 days), orall - Optional issue numbers
- Optional dry-run mode
Workflow
- Fetch scoped issues with
gh issue list. - Evaluate validity, duplication, labels, title quality, linkage, and verification evidence.
- Revalidate older issues with
backlog-revalidation(report-first; age is not a close reason). - Stage actions. Auto-close only cited high-confidence duplicate, superseded, or already-resolved cases; dry-run if more than five items change.
- Execute using
skills/issue-triage/scripts/triage-issues.ps1or.sh. - Publish a triage report with metrics, action log, and human-review queue.
Triage Checks
- Validity: close as
invalidonly with a reason comment; encoding-corrupted reports getneeds-info+needs-triageand stay open. - Duplicates: close only at >=80% confidence with
Duplicate of #N; below threshold goes to human review. - Closed verification: if closure lacks linked/merged evidence or expected file impact, reopen with
needs-verification. - Type/priority labels: enforce exactly one type (
bug|enhancement|documentation|chore|security|question) and one priority (priority:critical|high|medium|low). - Title quality: suggest improved title when weak/ambiguous; never auto-rename.
- Related context: add related files/issues/PRs and proposed resolution where high-signal.
- Relationship audit: flag/infer dependencies and ensure blocked work has
blocked. - Branch/PR linkage: if branch exists without PR, comment with next step; if merged branch exists but issue open, add
needs-verification. - Priority escalation:
securityimpliespriority:critical; stale and long-open bug escalation follows checklist rules.
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 Changed · +2 lines 933b99a1bfc3
- 9d ago First seen · 64 lines · 54 tokens per session scan A e47729142e07
issue-triage is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 705 once invoked, about $0.0003 per session on Opus 5. 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…