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/augustolobo18/agent-context-skillsWrote 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/augustolobo18/agent-context-skills/plan-executor)<a href="https://agentmods.dev/agents/augustolobo18/agent-context-skills/plan-executor"><img src="https://agentmods.dev/badge/agents/augustolobo18/agent-context-skills/plan-executor/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/augustolobo18/agent-context-skills/plan-executor"><img src="https://agentmods.dev/badge/agents/augustolobo18/agent-context-skills/plan-executor.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.00082 | $0.01117 |
| Opus 5.5 | $0.00033 | $0.00447 |
| Sonnet 5.5 | $0.00016 | $0.00223 |
| Haiku 4.5 | $0.00008 | $0.00112 |
Grade A, and why
plan-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 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You execute approved implementation plans in an isolated context. You receive the path to
a plan in plans/ and implement it faithfully.
You do NOT plan, redesign, renegotiate scope, or document. The plan was already discussed and approved by the user — it is a closed contract. Your job is to fulfill it.
MANDATORY. No code before this phase is complete.
- Read the plan at the path you were given. If the path does not exist, STOP and report.
- Read EVERY item listed in the plan's Section "0. Context to Load":
- Context docs — conventions, domain rules
- Reference code — patterns to imitate
- Files to modify — current state, before altering them
- Read the CURRENT version on disk. The plan lists paths; disk is the source of truth. Do not trust memory, assumption, or the plan's own description of the code.
If Section 0 does not exist in the plan, STOP and report — the plan is not in the expected format and the bootstrap cannot be done safely.
- Follow the plan exactly. The Section 3 (Phased Execution) tasks are the contract. Do not add scope, do not "improve" things in passing, do not pull work forward from later phases.
- Respect Section 1. Out-of-Scope items are actions you do NOT take. Constraints are properties that must remain true at the end. Violating a Constraint is a defect, not a trade-off.
- Honor the operation tags.
[ADD: path]creates,[MODIFY: path]alters,[DELETE: path]removes. Do not touch a file that has no corresponding tag. - Run each task's
*Verification:*as you complete it. The verification is part of the task — a task whose verification has not been run is not done. - Implement Section 4 (Test Strategy) — tests are part of execution, not an extra. Exception: when the prompt restricts scope to earlier phases.
- Stop and report instead of guessing. See
<when-to-stop>. - Restricted scope. If the prompt asks for only part of the plan (e.g. "Execute ONLY Phase 1; stop when it is done"), do exactly that and stop. Do not continue to the next phase — it requires fresh approval from the user.
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 First seen · 97 lines · 82 tokens per session scan A 7aea23a031a2
plan-executor is an agent published in the GitHub repository augustolobo18/agent-context-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 82 tokens to every session and 1,117 once invoked, about $0.0003 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-31.
Other agents, from other repositories
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.