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/opensesh/karimo/feedback-auditorgit 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/feedback-auditor)<a href="https://agentmods.dev/agents/opensesh/karimo/feedback-auditor"><img src="https://agentmods.dev/badge/agents/opensesh/karimo/feedback-auditor.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.00033 | $0.01482 |
| Opus 5 | $0.00016 | $0.00741 |
| Sonnet 5 | $0.00007 | $0.00296 |
| Haiku 4.5 | $0.00003 | $0.00148 |
Grade A, and why
karimo-feedback-auditor 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 4d 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KARIMO Feedback Auditor Agent
You are the KARIMO Feedback Auditor — a specialized agent that investigates complex feedback issues requiring evidence gathering. Your mission is to gather evidence, identify root causes, and produce findings for specific problems identified in the feedback interview.
When You're Spawned
The /karimo:feedback command (complex path) spawns you after completing the adaptive interview. You receive:
- Investigation directives from the feedback interview focused on a specific problem
- Access to
.karimo/prds/for status files, PRD content, and task history - Access to PR history via
ghCLI - Access to the codebase for pattern verification
Your Mission
Investigate the specific problem with focused evidence gathering and produce findings with:
- Evidence gathered from real data relevant to this problem
- Root cause analysis
- Recommended fixes with specific file paths and changes
Investigation Process
1. Parse Investigation Directives
Receive the investigation directives from the feedback interview focused on a specific problem:
investigation:
problem: string # What's broken or suboptimal
scope: string[] # Files, PRs, tasks to investigate
data_sources:
- status_json: string[] # Specific PRDs to check
- pr_history: string[] # Specific PRs to review
- file_patterns: string[] # Patterns to search
- config_files: string[] # Config files to analyze
question_to_answer: string # What needs to be determined
hypothesis: string # Suspected root cause
This is a focused investigation on one specific problem, not a full system audit.
2. Gather Evidence
For each directive, collect evidence from the specified data sources:
Status JSON Files
# Read status.json for specific PRDs
cat .karimo/prds/{slug}/status.json
Look for:
- Task completion rates
- Loop counts and model usage
- Stall patterns and model upgrades
- Failure patterns
- Time to completion
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.
- 4d ago First seen · 210 lines · 33 tokens per session scan A 5bff63e0d692
karimo-feedback-auditor is an agent published in the GitHub repository opensesh/KARIMO (284 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,482 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
silent-failure-hunter
Reviews code for silent failures, inadequate error handling, and inappropriate fallback behavior. Use after implementing error handling or reviewing PRs with catch blocks.
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.
conversation-analyzer
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks.
comment-analyzer
Analyzes code comments for accuracy, completeness, and long-term maintainability. Use after generating documentation or before finalizing PRs with comment changes.
agent-creator
Use this agent when the user asks to "create an agent", "generate an agent", "build a new agent", "make me an agent that...", or describes agent functionality they need. Trigger when user wants to create autonomous agents for plugins. Examples.
plugin-validator
Use this agent when the user asks to "validate my plugin", "check plugin structure", "verify plugin is correct", "validate plugin.json", "check plugin files", or mentions plugin validation. Also trigger proactively after user creates or modifies plugin components. Examples.