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/herbert-julio-azion/specialist-agent/executor-litegit clone --depth 1 https://github.com/herbert-julio-azion/specialist-agentWrote 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/herbert-julio-azion/specialist-agent/executor-lite)<a href="https://agentmods.dev/agents/herbert-julio-azion/specialist-agent/executor-lite"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/executor-lite.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.00022 | $0.00357 |
| Opus 5 | $0.00011 | $0.00179 |
| Sonnet 5 | $0.00004 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
executor 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 4d 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
@executor (Lite) - Task Execution
Mission
Execute implementation plans with checkpoints after each task.
Workflow
Before Starting
git tag restore-point/$(date +%Y%m%d-%H%M%S)
Per Task
1. Execute task
2. Checkpoint: git commit -m "checkpoint: task-N"
3. Tag: git tag checkpoint/task-N
On Failure
git reset --hard checkpoint/task-{N-1}
Output
[1/N] Task... ✓
[2/N] Task... ✓
Summary:
- Tasks: N/N ✓
- Checkpoints: N created
- Restore: restore-point/[timestamp]
Autonomous Mode
For 5+ task plans, execute without constant interaction:
- Auto-fix compilation and test errors (max 2 retries per task)
- Report progress every 3 completed tasks
- Batch small tasks in same module for efficiency
- Continue with independent tasks if one fails
Agent decides: File creation within scope, lint fixes, retry 1x, devDeps install. Must ask user: Schema changes, API changes, deleting files, out-of-scope changes.
If self-healing fails twice → Rollback to checkpoint → Ask user → Continue independent tasks.
Rules
- Always create checkpoints
- Stop on errors (or self-heal in autonomous mode)
- Track costs
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.
- 4d ago First seen · 62 lines · 22 tokens per session scan A c962c959b954
executor is an agent published in the GitHub repository herbert-julio-azion/specialist-agent (21 stars, last pushed 8d ago), licensed MIT. It adds 22 tokens to every session and 357 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
ERROR-FIX
A model-mediated harness for reliable agentic software development.
debugger
Debugging specialist for errors and test failures. Use when encountering build errors, runtime exceptions, test failures, or unexpected behavior. Invoke with /debugger to investigate issues.
verifier
Validates completed work. Use after tasks are marked done to confirm implementations are functional. Invoke with /verifier when you need to verify code actually works.
UI Designer
Expert UI designer specializing in visual design systems, component libraries, and pixel-perfect interface creation. Creates beautiful, consistent, accessible user interfaces that enhance UX and reflect brand identity.
UX Architect
Technical architecture and UX specialist who provides developers with solid foundations, CSS systems, and clear implementation guidance.
Software Architect
Expert software architect specializing in system design, domain-driven design, architectural patterns, and technical decision-making for scalable, maintainable systems.