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/a-ariff/ariff-claude-plugins/executing-plansnpx skills add a-ariff/ariff-claude-plugins --skill executing-plansgit clone --depth 1 https://github.com/a-ariff/ariff-claude-pluginsWrote 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/a-ariff/ariff-claude-plugins/executing-plans)<a href="https://agentmods.dev/skills/a-ariff/ariff-claude-plugins/executing-plans"><img src="https://agentmods.dev/badge/skills/a-ariff/ariff-claude-plugins/executing-plans.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.00013 | $0.00520 |
| Opus 5 | $0.00006 | $0.00260 |
| Sonnet 5 | $0.00003 | $0.00104 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
executing-plans 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
Executing Plans
Purpose
Execute plans in controlled batches with verification gates.
"I'm using the Executing Plans skill to implement this plan."
The Process
Load Plan → Review → Execute Batch → Report → Feedback → Next Batch
Step 1: Load & Review
- Read the plan file
- Review critically - identify concerns
- If concerns → Raise with user before starting
- Create TodoWrite for all tasks
Step 2: Execute Batch
Default batch size: 3 tasks
For each task:
- Mark as
in_progress - Follow each step exactly
- Run verifications as specified
- Mark as
completed
Step 3: Report
After each batch:
## Batch Complete
**Implemented:**
- Task 1: [summary]
- Task 2: [summary]
- Task 3: [summary]
**Verification:**
\`\`\`
[test output]
\`\`\`
Ready for feedback.
Step 4: Continue
Based on feedback:
- Apply changes if needed
- Execute next batch
- Repeat until complete
When to STOP
🛑 Stop immediately when:
- Hit a blocker (missing dependency, unclear instruction)
- Test fails unexpectedly
- Plan has gaps preventing progress
- You don't understand something
Ask for clarification. Don't guess.
Verification Rules
Before marking ANY task complete:
- Run the verification command
- Read the FULL output
- Confirm it matches expectations
- Only THEN mark complete
No "should work" or "looks good" - actual verification output.
Batch Reporting Format
### Batch N Complete
| Task | Status | Verification |
|------|--------|--------------|
| Task X | ✅ | 12/12 tests pass |
| Task Y | ✅ | Build successful |
| Task Z | ⚠️ | Needs review |
**Next batch:** Tasks A, B, C
Continue?
Completion
After all tasks:
- Run full test suite
- Verify all requirements met
- Report final status
- Hand off to
finishing-branchskill if applicable
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 · 110 lines · 13 tokens per session scan A 6e768da89cca
executing-plans is a skill published in the GitHub repository a-ariff/ariff-claude-plugins (14 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 520 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 skills, from other repositories
email-triage
Classify incoming emails into triage categories using content analysis, sender profile memory, and thread detection. Produces a category (URGENT, REPLYNEEDED, FYI, NEWSLETTER, NOTIFICATION, SPAM) with confidence and reasoning.
database-verification
Shell-based database connectivity and integrity checks. Verifies that databases are reachable, schemas match expectations, and data integrity constraints hold.
environment-diagnostics
Environment variable validation and configuration verification. Checks that required variables are set, config files parse correctly, ports are available, and system dependencies meet version requirements.
kubernetes
Diagnose and fix Kubernetes pods, services, networking, storage, and rollout failures with kubectl. Safety-first, read-only by default.
prompt-craft
Translate natural language image descriptions into detailed, structured DALL-E prompts with subject, style, composition, lighting, and mood specifications.
reply-composer
Draft context-aware email replies that match sender tone, reference thread history, and follow the user's style preferences. Presents drafts for review before sending.