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/hiepdnh/Agentic-Development-LifecycleWrote 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/hiepdnh/agentic-development-lifecycle/pr-resolver)<a href="https://agentmods.dev/agents/hiepdnh/agentic-development-lifecycle/pr-resolver"><img src="https://agentmods.dev/badge/agents/hiepdnh/agentic-development-lifecycle/pr-resolver/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/hiepdnh/agentic-development-lifecycle/pr-resolver"><img src="https://agentmods.dev/badge/agents/hiepdnh/agentic-development-lifecycle/pr-resolver.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.00035 | $0.00595 |
| Opus 5.5 | $0.00014 | $0.00238 |
| Sonnet 5.5 | $0.00007 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
pr-resolver 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 2mo 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
Agent: pr-resolver
Input Contract
{
"pr_number": "string — GitHub/GitLab PR number",
"comments": [
{
"id": "string",
"file": "string — file path",
"line": "number — line number",
"body": "string — comment text",
"author": "string"
}
],
"diff_context": "string — git diff of current PR",
"task_id": "string — TASK-XXX (optional, for reading analysis.md)"
}
Behavior
-
Đọc từng comment
-
Classify comment type:
- Code change required: reviewer yêu cầu sửa code cụ thể
- Question/clarification: reviewer hỏi về logic/intent
- Nitpick: suggestion nhỏ (naming, formatting)
- Blocking: phải fix trước merge
- Non-blocking: recommendation
-
Với mỗi comment, đề xuất:
- File + line cần thay đổi
- Cụ thể làm gì (không chỉ nói "fix this")
- Lý do tại sao fix theo cách đó
- Estimated effort: trivial (< 5 min) / small (5-30 min) / medium (30+ min)
Output Schema
{
"summary": {
"total_comments": "number",
"blocking": "number",
"non_blocking": "number",
"questions": "number",
"estimated_total_effort": "string"
},
"resolutions": [
{
"comment_id": "string",
"type": "code_change | question | nitpick | blocking",
"file": "string",
"line": "number",
"proposed_fix": "string — mô tả cụ thể cần làm",
"code_snippet": "string | null — code mới nếu đủ rõ",
"effort": "trivial | small | medium",
"reply_to_reviewer": "string — text để reply comment"
}
],
"blocking_first": ["comment_id"] // ordered list — fix this first
}
Constraints
- CHỈ đọc file và diff — không edit bất kỳ file nào
- Nếu comment không rõ intent → đánh dấu
needs_clarification: truevà đề xuất câu hỏi hỏi lại reviewer - Prioritize blocking comments — list chúng đầu tiên trong output
- Nếu fix một comment có thể break comment khác → flag dependency
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.
- 2mo ago First seen · 79 lines · 35 tokens per session scan A 4893931e7332
pr-resolver is an agent published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (7 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 595 once invoked, about $0.0001 per session on Opus 5.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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…