Forge is a command-line development environment that uses AI models as a pair programmer for working with code and shell commands. Developers use it to understand projects and carry out coding tasks through interactive, one-shot, or ZSH-based workflows. The catalogue entries extend Forge with reusable skills, agents, commands, and instructions.
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 tailcallhq/forgecode --skill execute-plangit clone --depth 1 https://github.com/tailcallhq/forgecodeWrote 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/tailcallhq/forgecode/execute-plan)<a href="https://agentmods.dev/skills/tailcallhq/forgecode/execute-plan"><img src="https://agentmods.dev/badge/skills/tailcallhq/forgecode/execute-plan/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/skills/tailcallhq/forgecode/execute-plan"><img src="https://agentmods.dev/badge/skills/tailcallhq/forgecode/execute-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.00423 |
| Opus 5.5 | $0.00018 | $0.00169 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 54 lines · 46 tokens per session scan A 9c8829abd296
execute-plan is a skill published in the GitHub repository tailcallhq/forgecode (7,638 stars, last pushed today), licensed Apache-2.0. It adds 46 tokens to every session and 423 once invoked, about $0.0002 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-30.
Other skills, from other repositories
anti-slop-design
Autonomous Principal Design Technologist. Cures vibe-coded software from AI frontend slop using curated token archetypes and 7-axis quality gating.
apify-integration-development
Curated upstream guidance for Apify Integration Development; use when the workflow matches the user goal.
agent-framework-azure-ai-py
Build persistent agents on Azure AI Foundry using the Microsoft Agent Framework Python SDK.
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
analytics-tracking
Design, audit, and improve analytics tracking systems that produce reliable, decision-ready data.
aria
Designs the data model, API contracts, and structural foundation of the system.