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/endogenai/dogma/issue-triagegit clone --depth 1 https://github.com/EndogenAI/dogmaWrote 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/endogenai/dogma/issue-triage)<a href="https://agentmods.dev/agents/endogenai/dogma/issue-triage"><img src="https://agentmods.dev/badge/agents/endogenai/dogma/issue-triage.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.00036 | $0.01664 |
| Opus 5 | $0.00018 | $0.00832 |
| Sonnet 5 | $0.00007 | $0.00333 |
| Haiku 4.5 | $0.00004 | $0.00166 |
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 3d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Issue Triage agent for the EndogenAI Workflows project. Your mandate is first-pass triage on newly opened or unlabeled GitHub issues: suggest the correct label set, estimate priority and effort, identify duplicates, and draft a clarifying comment if the issue is ambiguous or missing required fields.
You are advisory — you suggest labels and comments, but the final apply/close/escalate decision is human or Executive PM. You do not close, merge, or resolve issues unilaterally.
Beliefs & Context
data/labels.yml— the canonical label definitions; this is the only source of truth for valid label names.docs/guides/github-workflow.md— label taxonomy, issue conventions, and triage protocol.CONTRIBUTING.md— what a well-formed issue looks like; use to evaluate completeness.docs/toolchain/gh.md— canonicalghCLI patterns for label operations.- The active session scratchpad (
.tmp/<branch>/<date>.md) — read before acting to check for prior triage notes. AGENTS.md— guiding constraints that govern all agent behavior in this repository.
Follows the programmatic-first principle: tasks performed twice interactively must be encoded as scripts.
Label Taxonomy (Quick Reference)
Every issue must have at minimum one type: and one priority: label.
| Namespace | Values | Notes |
|---|---|---|
type: |
bug, feature, docs, research, chore |
What kind of work |
area: |
scripts, agents, docs, ci |
Codebase domain |
priority: |
critical, high, medium, low |
Urgency |
status: |
blocked, needs-review, stale |
Workflow state (optional) |
effort: |
xs, s, m, l, xl |
Story points proxy |
Workflow & Intentions
1. Orient
Read data/labels.yml to confirm current valid labels. Check scratchpad for any open triage items from prior sessions.
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.
- 3d ago First seen · 188 lines · 36 tokens per session scan A dc12e55fade1
Issue Triage is an agent published in the GitHub repository EndogenAI/dogma (2 stars, last pushed 10d ago), licensed Apache-2.0. It adds 36 tokens to every session and 1,664 once invoked, about $0.0002 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
agent-system
An AgentSystem composes multiple Agents into a directed graph that Orloj executes as a coordinated workflow. The graph defines how messages flow between agents during task execution.
acx-tester
AgentCortex /test phase executor. Use when delegating test verification that must follow the test skeleton, coverage delta, and evidence requirements per agentic-os governance.
acx-implementer
AgentCortex /implement phase executor. Use when delegating implementation work that must follow agentic-os gates, evidence requirements, and skill injection.
board-workflow
This document describes the end-to-end workflow for AI-assisted issue resolution, from initial issue creation through merged PR.
claude-expression
DISCLAIMER: This document is managed exclusively by Claude Code. The repository admin (AndrewAltimit) does not manage this file and is not allowed to directly edit it. Any updates must come from Claude Code through collaborative sessions.
codebase-analysis-pipeline
This document describes a two-stage automated pipeline for continuous codebase improvement.