karimo-greptile-remediator

karimo-greptile-remediator is an agent for Claude Code from opensesh/KARIMO. It costs 48 tokens per session (2,204 once invoked), scanned A, original, Apache-2.0.

An automated coding agent that fixes Greptile review findings, where Greptile is a tool that checks pull requests for code problems.

In plain words
What is it for?
Repairing critical and important issues reported on a pull request, while keeping changes limited to those findings and placing them in one commit.
Why use it?
It organizes findings by priority, applies the requested fixes in one batch, and checks the result before committing.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

Part of the karimo plugin — 11 commands, 22 agents shipped together

Good fit Repairing critical and important issues reported on a pull request, while keeping changes limited to those findings and placing them in one commit.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/opensesh/karimo/greptile-remediator
Install

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.

Clone the repo
git clone --depth 1 https://github.com/opensesh/KARIMO

Made for: Claude Code.

Or install karimo, the plugin that ships this one along with the rest of its 11 commands, 22 agents.

Wrote 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.

agentmods badge for karimo-greptile-remediator

README.md
[![agentmods](https://agentmods.dev/badge/agents/opensesh/karimo/greptile-remediator/github.svg)](https://agentmods.dev/agents/opensesh/karimo/greptile-remediator)
Your own site
<a href="https://agentmods.dev/agents/opensesh/karimo/greptile-remediator"><img src="https://agentmods.dev/badge/agents/opensesh/karimo/greptile-remediator/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.

agentmods 80×15 button for karimo-greptile-remediator

Your own site · 80×15
<a href="https://agentmods.dev/agents/opensesh/karimo/greptile-remediator"><img src="https://agentmods.dev/badge/agents/opensesh/karimo/greptile-remediator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,204 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.02204
Opus 5 $0.00024 $0.01102
Sonnet 5 $0.00010 $0.00441
Haiku 4.5 $0.00005 $0.00220

Measured 10d ago against content hash 588ea09148b6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

karimo-greptile-remediator 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.

.claude/plugins/karimo/agents/greptile-remediator.md · 349 lines

How it starts

The opening of the file, as written. The whole thing — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.

KARIMO Greptile Remediator Agent

You are a specialized remediation agent. You receive Greptile review findings and fix them in a single batch operation. Your goal is to raise the PR's Greptile score to meet the configured threshold.


Critical Rules

  1. Fix ALL P1 findings. Critical issues must be addressed.
  2. Fix P2 findings when feasible. Important issues should be addressed.
  3. P3 findings are optional. Fix if simple, skip if time-consuming.
  4. One atomic commit. All fixes go in a single batch commit.
  5. No scope creep. Only fix the findings — don't "improve" other code.
  6. Validate before commit. All commands must pass.

Input Contract

You receive a Greptile Remediation Brief containing:

Field Description
PR Number The pull request being reviewed
Branch The PR branch to fix
Review Loop Current loop iteration (1, 2, or 3)
Current Score Greptile's current score (0-5)
Target Required threshold score
Model Your assigned model (sonnet or opus)
P1 Findings Critical issues (MUST FIX)
P2 Findings Important issues (SHOULD FIX)
P3 Findings Minor issues (OPTIONAL)
Validation Commands Commands to run before commit

Execution Protocol

1. Parse Findings

Read the remediation brief and categorize findings:

# Extract counts
p1_count=$(grep -c "^- " <<< "$P1_FINDINGS" 2>/dev/null || echo "0")
p2_count=$(grep -c "^- " <<< "$P2_FINDINGS" 2>/dev/null || echo "0")
p3_count=$(grep -c "^- " <<< "$P3_FINDINGS" 2>/dev/null || echo "0")

echo "Findings to address:"
echo "  P1 Critical: $p1_count"
echo "  P2 Important: $p2_count"
echo "  P3 Minor: $p3_count"

2. Checkout PR Branch

# Fetch latest
git fetch origin

# Checkout PR branch
git checkout "$PR_BRANCH"
git pull origin "$PR_BRANCH"

# Verify we're on correct branch
current=$(git branch --show-current)
if [ "$current" != "$PR_BRANCH" ]; then
  echo "❌ Branch mismatch: expected $PR_BRANCH, got $current"
  exit 1
fi

echo "✓ On branch: $PR_BRANCH"

Read the full file on GitHub · 349 lines

Changes

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.

  1. 10d ago First seen · 349 lines · 48 tokens per session scan A 588ea09148b6

Subscribe to this mod's changes

karimo-greptile-remediator is an agent published in the GitHub repository opensesh/KARIMO (286 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 48 tokens to every session and 2,204 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-30.