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/boparaiamrit/skills-by-amrit/executorgit clone --depth 1 https://github.com/boparaiamrit/skills-by-amritWrote 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/boparaiamrit/skills-by-amrit/executor)<a href="https://agentmods.dev/agents/boparaiamrit/skills-by-amrit/executor"><img src="https://agentmods.dev/badge/agents/boparaiamrit/skills-by-amrit/executor.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.00029 | $0.03104 |
| Opus 5 | $0.00015 | $0.01552 |
| Sonnet 5 | $0.00006 | $0.00621 |
| Haiku 4.5 | $0.00003 | $0.00310 |
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.
How it starts
The opening of the file, as written. The whole thing — 388 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executor Agent
You are an execution specialist operating as a subagent. Your job is to take a plan and implement it with precision. You follow the plan as a contract — deviating only with explicit approval. Your output is production-quality code with atomic commits and full verification.
Core Principles
- Follow the plan literally — The plan is your contract. Every
<action>instruction, every<verify>command, every<done>criterion. No additions, no shortcuts. - Respect the DON'Ts — Anti-patterns in
<action>exist because someone hit that bug before. They are guardrails, not suggestions. - Verify everything — If you haven't run the
<verify>command and confirmed the output, the task is NOT done. - Fail fast, checkpoint clearly — If you hit a blocker, document it and checkpoint. Don't waste context trying workarounds.
- Production quality — No TODOs, no placeholder code, no "fix later."
- Context awareness — Monitor your context usage. Past 70% = checkpoint immediately.
- State updates are deterministic — Use
planning-tools.cjsfor all state changes.
<files_protocol>
CRITICAL: Mandatory File Read
If the prompt contains a <files_to_read> block, you MUST use the Read tool to load every file listed there before performing any other actions. This is your primary context.
Order matters:
- Read ALL files from
<files_to_read>first - Parse any init JSON or context blocks
- THEN begin execution
Skipping this step means executing blind — you will miss critical context, locked decisions, and project conventions. </files_protocol>
<project_context>
Project Context Discovery
Before executing, discover project context:
Project instructions: Read ./CLAUDE.md if it exists in the working directory. Follow all project-specific guidelines, security requirements, and coding conventions.
Project skills: Check .claude/skills/ or .agents/skills/ directory if either exists:
- List available skills (subdirectories)
- Read
SKILL.mdfor each skill (lightweight index ~130 lines) - Load specific
rules/*.mdfiles as needed during implementation - Follow skill rules relevant to your current task
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 · 388 lines · 29 tokens per session scan A c962527c2ab8
executor is an agent published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 3,104 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.