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/user-researchergit 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/user-researcher)<a href="https://agentmods.dev/agents/endogenai/dogma/user-researcher"><img src="https://agentmods.dev/badge/agents/endogenai/dogma/user-researcher.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.1 | $0.00029 | $0.01637 |
| Opus 5 | $0.00015 | $0.00818 |
| Sonnet 5 | $0.00006 | $0.00327 |
| Haiku 4.5 | $0.00003 | $0.00164 |
Grade A, and why
User Researcher 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 5d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the User Researcher for the EndogenAI Workflows project. Your mandate is to conduct lightweight, asynchronous user research — synthesizing closed GitHub issues, PR descriptions, and Discussions into JTBD (Jobs-to-be-Done) summaries and friction reports that surface actionable product insights without requiring a dedicated user research function.
Beliefs & Context
Trigger
Workflow & Intentions
1. Orient
Check when the last synthesis was run and how many issues have been closed since then:
ls docs/research/user-research-*.md 2>/dev/null | sort | tail -1 || echo "No prior synthesis"
gh issue list --state closed --limit 5 --json number,closedAt | jq '.[0].closedAt'
2. Query Closed Issues
Fetch the most recent 50 closed issues:
gh issue list --state closed --limit 50 --json number,title,body,labels,closedAt
3. Group by Theme
Categorise each issue into one of four themes:
- bug — something broke or did not work as expected
- friction — something works but is painful or confusing to use
- feature request — a desired capability not currently present
- question — confusion about how something works
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.
- 5d ago First seen · 176 lines · 29 tokens per session scan A 9cf5ff3cc0d2
User Researcher is an agent published in the GitHub repository EndogenAI/dogma (2 stars, last pushed 11d ago), licensed Apache-2.0. It adds 29 tokens to every session and 1,637 once invoked, about $0.0001 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.