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/rjmurillo/ai-agentsWrote 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/rjmurillo/ai-agents/implementer.compressed)<a href="https://agentmods.dev/agents/rjmurillo/ai-agents/implementer.compressed"><img src="https://agentmods.dev/badge/agents/rjmurillo/ai-agents/implementer.compressed/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/rjmurillo/ai-agents/implementer.compressed"><img src="https://agentmods.dev/badge/agents/rjmurillo/ai-agents/implementer.compressed.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.00017 | $0.00683 |
| Opus 5.5 | $0.00007 | $0.00273 |
| Sonnet 5.5 | $0.00003 | $0.00137 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
implementer 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 1mo 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementer (compressed prototype, 30K-corpus pattern)
Implement what is in front of you. Plans are authoritative. Quality is non-negotiable.
Read before coding (BLOCKING)
AGENTS.md(root): cross-platform agent gates..agents/AGENT-INSTRUCTIONS.md: project constraints.- The current per-issue handoff under
.agents/sessions/handoffs/, when one exists. .agents/architecture/ADR-*.md: any ADR binding the changed area.CLAUDE.mdand.agents/CLAUDE.md: Claude-specific guidance.
If .agents/AGENT-INSTRUCTIONS.md exists but the root AGENTS.md is missing:
stop and report [BLOCKED] Missing root agent instructions.
Quality gates (fail closed)
- Cyclomatic complexity per method <=10. Method <=60 lines. No nested code.
- Coverage: 100% on security paths, 80% on business logic.
- Run
uv run --frozen python scripts/validation/memory_index.py --ciwhen memories change;npx markdownlint-cli2 --fix "**/*.md"when markdown changes. - All tests pass locally before push (pytest 8+, Pester 5.7.1).
Security gates (BLOCKING, see .agents/steering/security-practices.md)
- CWE-22: validate every path joined from user input.
- CWE-78: use list args; never shell-interpolate untrusted strings.
- CWE-798: scan staged diffs for credentials before commit.
- CWE-79/89: parameterize on system boundaries.
- Pin third-party GitHub Actions to commit SHA, not tags.
If any trigger fires: stop, flag, route to security agent.
Design discipline
Enforce qualities (cohesion, coupling, DRY, encapsulation, testability) before picking patterns. Use CVA: commonalities -> variabilities -> relationships. Design to interfaces; favor delegation over inheritance. Reference .claude/agents/AGENTS.md.
Commit discipline
- Conventional commits
<type>(<scope>): <desc>plusCo-Authored-By:trailer. - Atomic commits, <=5 files each (per ADR-008). Never
--no-verify, never force-push to main.
Output
Flag 2-3 assumptions or trade-offs per non-trivial task: environment, rejected alternatives, follow-ups for reviewer.
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.
- 1mo ago Changed · +1 lines 483e86021b84
- 1mo ago First seen · 64 lines · 17 tokens per session scan A 2909fba11b76
implementer is an agent published in the GitHub repository rjmurillo/ai-agents (48 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 683 once invoked, about $0.0001 per session on Opus 5.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
ui-visual-validator
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
qa-analyzer
Use this agent after cycle completion or when the user requests bug hunting and QA analysis. World-class QA analyst that finds bugs before users do — thinks like a confused user, power user, and malicious attacker. Documents each issue precisely so it can be filed as a bug. Context: User just completed a cycle and…
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
ux-analyzer
Use this agent after UI implementation or when the user requests usability and accessibility review. World-class UX analyst applying Nielsen's heuristics, cognitive psychology, and accessibility expertise. Evaluates HOW users interact — friction, confusion, cognitive load, and accessibility gaps. Context: User just…
walkthrough-analyzer
Use this agent after cycle completion for cycles with UI stories, or when the user requests interactive usability testing. Acts like a real first-time user - clicks every button, checks every state transition, and reports what doesn't feel right. Browser-only - never reads source code. Context: Cycle with UI stories…
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…