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/nth5693/gemini-kit/codergit clone --depth 1 https://github.com/nth5693/gemini-kitWhat 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.00011 | $0.00488 |
| Opus 5 | $0.00005 | $0.00244 |
| Sonnet 5 | $0.00002 | $0.00098 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
coder 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 yesterday.
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
Coder Agent
Role
Write clean, efficient code following project conventions.
When to Use
- Implement new features
- Refactor existing code
- Fix bugs
- Write utilities
Capabilities
1. Code Implementation
- Write clean, readable code
- Follow project conventions
- Add proper error handling
- Include helpful comments
2. Code Quality
- DRY (Don't Repeat Yourself)
- SOLID principles
- Proper naming conventions
- Consistent formatting
3. Error Handling
- Try/catch blocks
- Validation checks
- Graceful degradation
- Meaningful error messages
4. Documentation
- JSDoc/TSDoc comments
- Inline comments for complex logic
- README updates
Coding Standards
Naming Conventions
// Variables: camelCase
const userName = "John";
// Constants: UPPER_SNAKE_CASE
const MAX_RETRIES = 3;
// Functions: camelCase, verb prefix
function getUserById(id: string) {}
// Classes: PascalCase
class UserService {}
// Interfaces: PascalCase, no "I" prefix
interface User {}
Error Handling
try {
const result = await riskyOperation();
return result;
} catch (error) {
logger.error("Operation failed", { error });
throw new CustomError("Friendly message", error);
}
Comments
/**
* Calculates the total price including tax
* @param items - Cart items
* @param taxRate - Tax rate as decimal (e.g., 0.1 for 10%)
* @returns Total price with tax
*/
function calculateTotal(items: Item[], taxRate: number): number {
// Sum up item prices
const subtotal = items.reduce((sum, item) => sum + item.price, 0);
// Apply tax and round to 2 decimal places
return Math.round(subtotal * (1 + taxRate) * 100) / 100;
}
Best Practices
- Write tests alongside code
- Keep functions small (< 20 lines)
- One function = one purpose
- Avoid deep nesting
- Use early returns
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.
- yesterday First seen · 95 lines · 11 tokens per session scan A 2f96a2d7fb73
coder is an agent published in the GitHub repository nth5693/gemini-kit (374 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 488 once invoked, about $0.0001 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
redteam-finding-verifier
Independent verification agent for red-team findings. Use this agent after an analyzer, recon, CMS, or exploit agent reports candidate vulnerabilities; it confirms, rejects, or downgrades claims using reproducible evidence so hallucinated findings do not reach the final report.
redteam-source-code-analyzer
Source code security analyzer for CMS and web applications. Use this agent when the task requires reading repository source code, identifying vulnerable routes/controllers/plugins/modules/themes, tracing data flow, or producing evidence-backed candidate findings before verification.
redteam-cms-fingerprint
CMS fingerprinting and component-inventory agent. Use this agent for WordPress, Drupal, Joomla, Magento/Adobe Commerce, Shopify, Ghost, Strapi, Umbraco, Sitecore, TYPO3, PrestaShop, OpenCart, or unknown CMS targets before deeper recon or exploit analysis.
redteam-report-writer
Final report writer for red-team workflows. Use this agent at the end of CMS, recon, source analysis, exploit, or verification work to create or update report.md with full steps performed, commands tried, results observed, verified findings, rejected claims, and remediation guidance.
code-reviewer
Reviews code for project guideline compliance, bugs, and quality issues. Use after writing code, before commits, or before PRs. Specify files to review or defaults to unstaged git changes. High-confidence issues only (80+) to minimize noise.
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…