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 skills add rjmurillo/ai-agents --skill execution-plansgit clone --depth 1 https://github.com/rjmurillo/ai-agentsWrote 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/rjmurillo/ai-agents/execution-plans)<a href="https://agentmods.dev/skills/rjmurillo/ai-agents/execution-plans"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/execution-plans.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 12 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Rogue Agent · line 63 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00061 | $0.00902 |
| Opus 5 | $0.00030 | $0.00451 |
| Sonnet 5 | $0.00012 | $0.00180 |
| Haiku 4.5 | $0.00006 | $0.00090 |
Grade A, and why
execution-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.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execution Plans Skill
Treat execution plans as first-class artifacts, versioned in the repository.
Directory Structure
.agents/
├── plans/
│ ├── active/ # Plans currently in progress
│ ├── completed/ # Successfully finished plans
│ └── abandoned/ # Plans that were stopped (with rationale)
└── debt/
└── tech-debt-registry.md # Known technical debt items
Triggers
| Trigger Phrase | Operation |
|---|---|
create execution plan |
Create new plan in active/ |
update plan progress |
Add progress entry to existing plan |
log decision |
Add decision to plan's decision log |
complete plan |
Move plan to completed/ |
abandon plan |
Move plan to abandoned/ with rationale |
Plan Template
Use .agents/plans/TEMPLATE.md as the starting point for new plans.
Required Sections
| Section | Purpose |
|---|---|
| Metadata | Status, dates, owner, complexity |
| Objectives | Checkboxes for trackable goals |
| Decision Log | Table of decisions with rationale |
| Progress Log | Timestamped updates with agent attribution |
| Blockers | Current impediments |
| Related | Links to issues, PRs, ADRs |
Process
Creating a Plan
- Copy TEMPLATE.md to
.agents/plans/active/{slug}.md - Fill metadata (status: In Progress, created: today, owner: agent name)
- Define objectives as checkboxes
- Link to related issue/PR
Updating Progress
- Check off completed objectives
- Add entry to Progress Log table with date, update, and agent name
- Update blockers if any emerge
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 · 122 lines · 61 tokens per session scan A 5fce18066fe3
execution-plans is a skill published in the GitHub repository rjmurillo/ai-agents (45 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 902 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
linear-cli
Use when the user wants to list, view, start, create, or update Linear issues from the terminal via schpet/linear-cli, including setup, auth, repo config, and safe read/write boundaries.
ci-cd
A guide for designing automated build and delivery workflows with GitHub Actions. These workflows can run checks such as tests, code-quality scans, coverage checks, and builds when code is pushed or a pull request is opened.
crew-lifecycle
Use this skill when coordinating a live crew across hierarchy, approvals, and boards.
team-plan-review
Use this skill when leading a crew that must submit an execution plan before work starts.
proactive-memory
Turn repeated failures, corrections, and recurring requests into durable follow-up work.
matrix-ops
Use Matrix when work crosses rooms, bridges, or federated teams that need durable plain-text coordination.