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 fakoli/fakoli-plugins --skill executegit clone --depth 1 https://github.com/fakoli/fakoli-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/fakoli/fakoli-plugins/execute)<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/execute"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/execute/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/fakoli/fakoli-plugins/execute"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/execute.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00016 | $0.04696 |
| Opus 5.5 | $0.00006 | $0.01878 |
| Sonnet 5.5 | $0.00003 | $0.00939 |
| Haiku 4.5 | $0.00002 | $0.00470 |
Grade A, and why
execute 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.
How it starts
The opening of the file, as written. The whole thing — 495 lines — stays where its author put it; the contents beside it link to each section on GitHub.
In Codex, first read the native runtime adapter.
Execute — Execute Phase
Load an intent-driven plan, group tasks into dependency-ordered waves, dispatch specialist agents in parallel within each wave, run language-aware verification and a mandatory critic gate between waves, then dispatch the sentinel for final sign-off.
In the supported Claude hook context, dispatch ordering is mechanically tracked: while a run is armed (see Step 1), the plugin's PreToolUse hook denies dispatch of any agent other than critic or welder once a code-writing agent has completed and the critic has not yet reviewed. The orchestrator must still inspect the review verdict; hook completion does not establish PASS. In Codex the adapter disables these legacy hooks and enforces the gate through explicit review evidence. Arm/disarm only the compatible Claude gate; skip the arming-file steps in Codex.
Process Flow
Start
|
v
[1. Load plan]
Parse tasks, dependencies, agent assignments, verify commands.
|
v
[2. Detect agents]
Is fakoli-crew installed? Log available agents. Note fallback.
|
v
[3. Group into waves]
Apply dependency rules (see Wave Assignment section below).
|
v
[For each wave:]
|
v
[a. Dispatch agents in parallel]
One Agent tool call per task. All tasks in the wave start simultaneously.
|
[b. Wait for completion]
Read agent status files. Poll until all show COMPLETE, BLOCKED, or NEEDS_REVIEW.
|
[c. Handle escalations]
BLOCKED -> surface to user, wait for resolution, then re-dispatch.
NEEDS_REVIEW -> surface to user, wait for decision, then continue.
|
[d. Run language verification]
TypeScript: npx tsc --noEmit
Python: ruff check . && mypy .
Rust: cargo check
If fail -> dispatch welder to fix -> re-run verification.
Do NOT proceed to critic until verification passes.
|
[e. Run critic gate (non-negotiable)]
Collect modified files from status files.
Dispatch critic with file list + acceptance criteria.
PASS or SHOULD FIX/NIT -> proceed.
MUST FIX -> enter fix cycle (max 3 iterations, then escalate).
|
v
[After all waves: Dispatch sentinel]
Final verification with evidence gate.
|
v
[Report summary]
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 Changed · +6 lines 2fd120d627d4
- 1mo ago First seen · 489 lines · 16 tokens per session scan A 010d024da1f4
execute is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 24d ago), licensed MIT. It adds 16 tokens to every session and 4,696 once invoked, about $0.0001 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-31.
Other skills, from other repositories
issue-triage
Use when the user wants to triage GitHub issues - decide whether an issue is still relevant, reproducible, closeable, a duplicate, or what concretely needs doing. Selects and prioritizes first (never dumps all issues at once), then deep-triages the chosen issues via parallel subagents, recommends actions for the owner…
requirements-verbatim
Capture a user requirement, decision, approval, or constraint word-for-word into an append-only dated log so it survives context compaction and can never be trimmed, softened, or reinterpreted. Use whenever the user states or approves a requirement, gives a GO, sets a constraint, or makes any decision that later work…
work-planning
Design the complete work hierarchy for a Paperclip company — Goals, Projects, and Tasks as a unified top-down planning workflow. Produces .planning.json for deterministic generation of goals/, projects/, and tasks/ directories. Use when creating a new company's work plan, reorganizing work structure, or linking goals…
project
A single starting point for setting up an AI-assisted project in Claude Cowork. It asks questions about the work, reviews available add-ons, and creates project instructions, custom agents, and connected workflows.
hr-operations
A skill for designing remote-work and team-operation policies. It covers flexible work, asynchronous communication, collaboration tools, productivity tracking, and employee experience.
hr-performance-review
A skill for designing and running employee performance reviews. It covers MBO, OKRs, KPIs, 360-degree feedback, review guides, and feedback conversations; OKRs set goals and measurable results, while KPIs track ongoing performance.