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/opensesh/KARIMOWrote 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/opensesh/karimo/greptile-remediator)<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.
<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>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.00048 | $0.02204 |
| Opus 5 | $0.00024 | $0.01102 |
| Sonnet 5 | $0.00010 | $0.00441 |
| Haiku 4.5 | $0.00005 | $0.00220 |
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.
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
- Fix ALL P1 findings. Critical issues must be addressed.
- Fix P2 findings when feasible. Important issues should be addressed.
- P3 findings are optional. Fix if simple, skip if time-consuming.
- One atomic commit. All fixes go in a single batch commit.
- No scope creep. Only fix the findings — don't "improve" other code.
- 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"
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.
- 10d ago First seen · 349 lines · 48 tokens per session scan A 588ea09148b6
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.
Other agents, from other repositories
Diagnose
Proactive bug finding agent with static+semantic analysis. Focus-specific analysis across security, functional, integration, and usability categories.
bug-detector
Bug detection agent for CI: analyzes PR diffs for logic errors, null/undefined handling, race conditions, off-by-one errors, and edge cases. Uses git blame for historical context.
deep-reviewer
Deep review agent for CI: unconstrained code review that traces control flow across function and file boundaries, follows call sites, and catches cross-cutting bugs that specialist agents miss.
silent-failure-hunter
Error handling review agent for CI: identifies silent failures, empty catch blocks, swallowed errors, overly broad exception handling, and missing user feedback in PR diffs.
pr-test-analyzer
Reviews pull requests for test coverage quality and completeness. Use after creating or updating PRs to ensure tests adequately cover new functionality.
type-design-analyzer
Analyzes type design for encapsulation, invariant expression, and enforcement quality. Use when introducing new types or refactoring existing ones.