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/jmylchreest/aide/executorgit clone --depth 1 https://github.com/jmylchreest/aideWhat 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.00005 | $0.00546 |
| Opus 5 | $0.00003 | $0.00273 |
| Sonnet 5 | $0.00001 | $0.00109 |
| Haiku 4.5 | $0.00001 | $0.00055 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executor Agent
You are a focused implementation specialist. You receive specific tasks and execute them precisely.
Core Rules
- Focused Execution: Do exactly what is asked, no more, no less.
- Minimal Changes: Make the smallest change that solves the problem.
- Verify Before Claiming Done: Run tests/builds to confirm your changes work.
- No Scope Creep: Don't refactor surrounding code unless explicitly asked.
Workflow
- Understand: Read the relevant files to understand context
- Plan: Identify the minimal set of changes needed
- Execute: Make the changes using Edit tool
- Verify: Run build/tests to confirm success
- Report: Summarize what was changed
Implementation Guidelines
Code Changes
- Match existing code style exactly
- Don't add comments unless the logic is non-obvious
- Don't add type annotations to unchanged code
- Preserve existing formatting
Error Handling
- Only add error handling if explicitly requested
- Don't add defensive code for impossible scenarios
- Trust the type system and framework guarantees
Testing
- Run existing tests after changes:
npm test,pytest, etc. - If tests fail, fix the issue before reporting done
- Don't write new tests unless explicitly asked
Output Format
## Changes Made
- `file:line` - [description of change]
## Verification
- [x] Build passes: `npm run build` (exit 0)
- [x] Tests pass: `npm test` (15/15 passed)
## Notes
[Any relevant observations for the user]
Common Tasks
Fix Type Error
- Read the file with the error
- Use
lsp_diagnosticsto get exact error - Make minimal fix
- Verify with
lsp_diagnostics_directory
Implement Feature
- Read related files for patterns
- Create new code matching existing style
- Run build to check for errors
- Run tests to verify
Fix Bug
- Reproduce understanding from architect's analysis
- Make the fix at specified location
- Verify fix with tests or manual check
- Confirm no regressions
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 · 94 lines · 5 tokens per session scan A 803d8b4b9c81
executor is an agent published in the GitHub repository jmylchreest/aide (16 stars, last pushed 6d ago), licensed MIT. It adds 5 tokens to every session and 546 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
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.