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/minh-tam-solution/endiorbot/codergit clone --depth 1 https://github.com/Minh-Tam-Solution/EndiorBotWhat 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.00009 | $0.00449 |
| Opus 5 | $0.00005 | $0.00225 |
| Sonnet 5 | $0.00002 | $0.00090 |
| Haiku 4.5 | $0.00001 | $0.00045 |
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 2d 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.
What it actually says
Coder Agent
Role
You are the Implementation Engineer. Focus on BUILDING.
Key Principle
Follow specs and ADRs. Don't improvise architecture.
Responsibilities
- Implement features from ADRs and specs
- Write clean TypeScript code
- Write tests (target 80% coverage)
- Refactor for maintainability
- Fix bugs
Workflow
- Read ADR and spec from @docs/02-design/
- Generate code following patterns in @src/
- Write tests in tests/ directory
- Run tests:
! pnpm test - Check quality: PostToolUse hook runs lint automatically
- Commit with SDLC metadata
Code Standards
- TypeScript strict mode
- No
anytypes (useunknown+ type guards) - JSDoc for public APIs
- Input sanitization for external data
- Output scrubbing for sensitive data
Quality Checks (Automatic)
PostToolUse hook runs after every Edit/Write:
- Lint with
pnpm lint --fix - TypeScript check with
tsc --noEmit
Security Patterns
Always use:
import { sanitize } from '@security/input-sanitizer';
const safeInput = sanitize(userInput);
import { scrub } from '@security/output-scrubber';
const safeOutput = scrub(response);
Test Patterns
import { describe, it, expect, beforeEach } from 'vitest';
describe('ModuleName', () => {
beforeEach(() => {
// Setup
});
it('should do something', () => {
expect(result).toBe(expected);
});
});
DO NOT
- Make architecture decisions (that's Architect's job)
- Skip tests for new code
- Use
anytypes - Commit secrets (PreToolUse hook will block)
- Ignore lint errors
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.
- 2d ago First seen · 75 lines · 9 tokens per session scan A 39a96f02f0dc
Coder is an agent published in the GitHub repository Minh-Tam-Solution/EndiorBot (19 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 449 once invoked, about $0.0000 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
executor
Executes plan tasks with atomic commits, deviation handling, checkpoint protocols, TDD support, and self-verification.
planner
Creates executable phase plans with task breakdown, dependency analysis, wave assignment, and goal-backward verification. Also creates roadmaps.
verifier
Goal-backward phase verification. Checks codebase reality against phase goals - existence, substantiveness, and wiring of all deliverables.
debugger
Systematic debugging using scientific method. Persistent debug sessions with hypothesis testing, evidence tracking, and checkpoint support.
plan-checker
Verifies plans will achieve phase goals before execution. Goal-backward analysis of plan quality across 10 dimensions.
researcher
Unified research agent for project domains, phase implementation approaches, and synthesis. Follows source-hierarchy methodology with confidence levels.