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 skills/savedpixel/ai-agent-rules-generator/execute-plannpx skills add savedpixel/ai-agent-rules-generator --skill execute-plangit clone --depth 1 https://github.com/savedpixel/ai-agent-rules-generatorWrote 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/skills/savedpixel/ai-agent-rules-generator/execute-plan)<a href="https://agentmods.dev/skills/savedpixel/ai-agent-rules-generator/execute-plan"><img src="https://agentmods.dev/badge/skills/savedpixel/ai-agent-rules-generator/execute-plan.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.00032 | $0.00616 |
| Opus 5 | $0.00016 | $0.00308 |
| Sonnet 5 | $0.00006 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
execute-plan 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 3d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute Implementation Plan
You have been given a plan file. Your job is to implement it fully — code, test, document, and close out.
Instructions
1. Read the Plan
- Read the attached plan file completely.
- Understand every section: Context, Current State, Target State, Implementation Steps, Testing Plan, Post-Implementation Checklist.
- Note the gate structure.
2. Review Recent Context
- Read latest task log(s) in
docs/task/logs/. - Read
docs/task/todo.mdfor conflicts. - Read
docs/task/lessons.mdfor relevant lessons. - Read agent observation logs in
docs/agent-observations/for relevant unresolved items.
If the plan is stale or conflicts, STOP and tell the user.
3. Execute Implementation Steps
Work through each step in order:
- Mark checkboxes as you complete them.
- Follow exact file paths, line numbers, and descriptions.
- If line numbers have drifted, locate by context.
- If blocked or plan is wrong, STOP and tell the user.
4. Execute Testing Plan (BLOCKING)
After ALL implementation steps, execute the Testing Plan:
- Run every Automated Check.
- Execute every Browser Verification step using Chrome MCP tools. Log in at
http://localhost:8080/wp-admin(admin/password). Resize to 1900×1200. - Execute every Regression Check.
- Verify Edge Cases.
Reading code is not testing. You must use Chrome MCP tools for UI verification. If any test fails, fix and re-test.
5. Documentation & Logging (only after testing passes)
- Update affected documentation per the trigger map in
AGENTS.md. - Add task log entry to today's
docs/task/logs/YYYY-MM-DD.md. - Log observations to
docs/agent-observations/. If none: "Observations: none."
6. Close Out
- Update plan status to Complete.
- Mark all Post-Implementation Checklist items checked.
- Remove task from
docs/task/todo.md. - Move plan file from
draft/tocompleted/. - Confirm to user: what was done, what was tested, result.
Rules
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.
- 3d ago First seen · 68 lines · 32 tokens per session scan A 2b0becc08166
execute-plan is a skill published in the GitHub repository savedpixel/ai-agent-rules-generator (7 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 616 once invoked, about $0.0002 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 skills, from other repositories
jira-cli
Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.
azure-prices
Look up and compare Azure service pricing using the Azure Retail Prices API. Use this skill whenever the user asks about Azure costs, pricing, rates, or wants to compare prices across regions or services — even if they don't say "pricing" explicitly. Trigger for questions like "how much does a D2 v2 VM cost?"…
calculator
Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.
az-cli
Use the Azure CLI (az) to manage Azure resources from the command line. Trigger this skill whenever the user asks to create, configure, manage, deploy, or interact with any Azure resource — even if they don't explicitly mention "az cli". Also trigger when the user asks about Azure CLI commands, syntax, or wants to…
code-review
Use when user wants code reviewed for correctness, style, bugs, and maintainability. Triggers on: review code, code review, check PR, 審查程式碼, 檢查程式碼. Produces severity-classified findings with a verdict. Do NOT use for security-focused audit (prefer security-audit) or SQL-focused review (prefer sql-review).
plan
Use when user needs a phased implementation plan with requirements, file impact, risks, and alternatives before coding — including clarifying vague or ambiguous requirements first. Triggers on: plan, how should we build, unclear requirements, 規劃, 幫我想方案. Produces a structured plan document. Do NOT use for atomic task…