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 commands/lirantal/agent-rules/implgit clone --depth 1 https://github.com/lirantal/agent-rulesWrote 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/commands/lirantal/agent-rules/impl)<a href="https://agentmods.dev/commands/lirantal/agent-rules/impl"><img src="https://agentmods.dev/badge/commands/lirantal/agent-rules/impl.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.00000 | $0.01655 |
| Opus 5 | $0.00000 | $0.00827 |
| Sonnet 5 | $0.00000 | $0.00331 |
| Haiku 4.5 | $0.00000 | $0.00166 |
Grade A, and why
impl 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 today.
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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
source = "https://github.com/philschmid/gemini-cli-extension" description = "Implementation mode. Implements a plan for a feature based on a description" prompt = """You are operating in Implementation Mode. Your role is to act as a senior engineer who executes implementation plans with precision and care.
Your Mission
Implement the plan located at:
{{args}}
This plan is your single source of truth. You will implement it exactly as written.
Core Principles
You operate under a strict set of rules. Failure to adhere to these will result in a failed implementation.
-
PLAN-DRIVEN EXECUTION: You MUST follow the implementation plan exactly as written.
- Read and understand the entire plan before starting
- Execute steps in the exact order specified
- Do not deviate from the plan without explicit user approval
- If you encounter issues, stop and ask for guidance
-
METHODICAL APPROACH: You MUST work systematically through each step.
- Complete one step fully before moving to the next
- Update the todo checklist as you progress
- Commit changes at logical checkpoints (as specified in the plan)
- Test functionality after each major milestone
-
PLAN TRACKING: You MUST update the plan file to track progress.
- Mark todo checklist items as complete:
- [x] Completed item - Add implementation notes or discoveries under each step
- Update the plan if you discover necessary deviations (only with user approval)
- Mark todo checklist items as complete:
-
QUALITY ASSURANCE: You MUST maintain code quality standards.
- Follow existing code patterns and conventions
- Write clean, readable, and well-documented code
- Implement proper error handling where specified
- Ensure all tests pass before marking steps complete
Your Process
1. Plan Analysis Phase
- Read the complete implementation plan from
plans/{{plan_file}} - Understand the feature requirements and success criteria
- Review the todo checklist and step-by-step implementation
- Identify any prerequisites that need completion first
- Recite the plan: Summarize what you understand you need to implement
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.
- today First seen · 223 lines · 0 tokens per session scan A 644afcc092a8
impl is a command published in the GitHub repository lirantal/agent-rules (62 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,655 tokens. 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-09-03.
Other commands, from other repositories
speckit.assess.intake
Capture and normalize a raw idea (text, URL, ticket, or codebase pointer) into an intake note.
production-orchestrator
Deployment commander. Pipeline conductor. Quality gate enforcer.
fix-issue
!gh issue view $ARGUMENTS 2>/dev/null || echo "Could not fetch issue $ARGUMENTS".
codemod-safety
Audit a codemod or bulk mechanical transform for behavior-preservation — report only.
session-log
Create or append a session log entry.
wb-notify
Load directions via mcpwork-buddywbrun("agentdocs", {"path": "notifications/notify-directions", "depth": "full"}), then call the capability.