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/tailcallhq/forgecode/execute-plannpx skills add tailcallhq/forgecode --skill execute-plangit clone --depth 1 https://github.com/tailcallhq/forgecodeWhat 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.00046 | $0.00423 |
| Opus 5 | $0.00023 | $0.00211 |
| Sonnet 5 | $0.00009 | $0.00085 |
| Haiku 4.5 | $0.00005 | $0.00042 |
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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- execute-plan — 100% identical, 0 lines differ
What it actually says
Execute Plan
Execute structured task plans with automatic status tracking and progress updates.
Commitment to Completion
When a plan is provided, all tasks in the plan must be completed. Before starting execution, recite:
"I will execute this plan to completion. All the 20 tasks will be addressed and marked as DONE."
Execution Steps
STEP 1: Recite the commitment to complete all tasks in the plan.
STEP 2: Read the entire plan file to identify pending tasks based on task_status.
STEP 3: Announce the next pending task and update its status to IN_PROGRESS in the plan file.
STEP 4: Execute all actions required to complete the task and mark the task status to DONE in the plan file.
STEP 5: Repeat from Step 3 until all tasks are marked as DONE.
STEP 6: Re-read the plan file to verify all tasks are completed before announcing completion.
Task Status Format
Use these status indicators in the plan file:
[ ]: PENDING
[~]: IN_PROGRESS
[x]: DONE
[!]: FAILED
Example Usage
- User provides: "Execute plan at plans/2025-11-23-refactor-auth-v1.md"
- Recite commitment: "I will execute this plan to completion..."
- Read the plan file
- Find first
[ ](PENDING) task - Update to
[~](IN_PROGRESS) - Execute the task
- Update to
[x](DONE) - Move to next PENDING task
- Repeat until all tasks appear DONE
- Re-read plan file to verify completion
- Announce completion
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.
- yesterday First seen · 54 lines · 46 tokens per session scan A 9c8829abd296
execute-plan is a skill published in the GitHub repository tailcallhq/forgecode (7,599 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 423 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-30.
Other skills, from other repositories
agent-framework-azure-ai-py
Build persistent agents on Azure AI Foundry using the Microsoft Agent Framework Python SDK.
agentmail
Email infrastructure for AI agents. Create accounts, send/receive emails, manage webhooks, and check karma balance via the AgentMail API.
aria
Designs the data model, API contracts, and structural foundation of the system.
max
Cleans up and improves existing code without changing behavior.
accint-commitments
Triage acc's open promises and close them with honest real-world verdicts via accact(runtime="outcome").
empirica-constitution
Empirica deep governance — phase-aware completion, the cognitive immune system, the turtle principle, and the practice model. Load this when the system prompt's operational routing isn't enough — when you need the why underneath the mechanism choice, or when "what counts as done" / "what is this practice" is the…