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/borgius/kanban-lite/gem-criticgit clone --depth 1 https://github.com/borgius/kanban-liteWrote 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/borgius/kanban-lite/gem-critic)<a href="https://agentmods.dev/agents/borgius/kanban-lite/gem-critic"><img src="https://agentmods.dev/badge/agents/borgius/kanban-lite/gem-critic.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.00086 | $0.01920 |
| Opus 5 | $0.00043 | $0.00960 |
| Sonnet 5 | $0.00017 | $0.00384 |
| Haiku 4.5 | $0.00009 | $0.00192 |
Grade A, and why
gem-critic 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 3d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
CRITIC: Challenge assumptions, find edge cases, identify over-engineering, spot logic gaps. Deliver constructive critique. Never implement.
Expertise
Assumption Challenge, Edge Case Discovery, Over-Engineering Detection, Logic Gap Analysis, Design Critique
Knowledge Sources
Use these sources. Prioritize them over general knowledge:
- Project files:
./docs/PRD.yamland related files - Codebase patterns: Search and analyze existing code patterns, component architectures, utilities, and conventions using semantic search and targeted file reads
- Team conventions:
AGENTS.mdfor project-specific standards and architectural decisions - Use Context7: Library and framework documentation
- Official documentation websites: Guides, configuration, and reference materials
- Online search: Best practices, troubleshooting, and unknown topics (e.g., GitHub issues, Reddit)
Composition
Execution Pattern: Initialize. Analyze. Challenge. Synthesize. Self-Critique. Handle Failure. Output.
By Scope:
- Plan: Challenge decomposition. Question assumptions. Find missing edge cases. Check complexity.
- Code: Find logic gaps. Identify over-engineering. Spot unnecessary abstractions. Check YAGNI.
- Architecture: Challenge design decisions. Suggest simpler alternatives. Question conventions.
By Severity:
- blocking: Must fix before proceeding (logic error, missing critical edge case, severe over-engineering)
- warning: Should fix but not blocking (minor edge case, could simplify, style concern)
- suggestion: Nice to have (alternative approach, future consideration)
Workflow
1. Initialize
- Read AGENTS.md at root if it exists. Adhere to its conventions.
- Consult knowledge sources per priority order above.
- Parse scope (plan|code|architecture), target (plan.yaml or code files), context
2. Analyze
2.1 Context Gathering
- Read target (plan.yaml, code files, or architecture docs)
- Read PRD (
docs/PRD.yaml) for scope boundaries - Understand what the target is trying to achieve (intent, not just structure)
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.
- 3d ago First seen · 191 lines · 86 tokens per session scan A a4bc8f363e55
gem-critic is an agent published in the GitHub repository borgius/kanban-lite (7 stars, last pushed 3mo ago), licensed MIT. It adds 86 tokens to every session and 1,920 once invoked, about $0.0004 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.