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 ABilenduke/copilot-developer --skill executegit clone --depth 1 https://github.com/ABilenduke/copilot-developerWrote 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/abilenduke/copilot-developer/execute)<a href="https://agentmods.dev/skills/abilenduke/copilot-developer/execute"><img src="https://agentmods.dev/badge/skills/abilenduke/copilot-developer/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/abilenduke/copilot-developer/execute"><img src="https://agentmods.dev/badge/skills/abilenduke/copilot-developer/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.00109 | $0.05737 |
| Opus 5.5 | $0.00044 | $0.02295 |
| Sonnet 5.5 | $0.00022 | $0.01147 |
| Haiku 4.5 | $0.00011 | $0.00574 |
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 — 606 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Executor Skill
Purpose
This skill takes a plan created by /plan and works through it step by step on a dedicated git branch. It uses a two-tier verification system:
- Per-step ralph loops (fast) — run relevant tests and lint after each step, fix failures iteratively
- Final ralph loop (deep) — a structured multi-phase review that goes beyond "do tests pass" into self-review, adversarial testing, and acceptance verification
A companion journal records everything — implementation details, verification results, fixes, and commit hashes.
First Steps
When this skill is invoked:
- Read
templates/journal-template.mdto understand the journal format - Read
examples/example-journal.mdto see the expected quality - Locate the plan:
- If the user specified a path, use that
- If not, check
docs/features/for available plans. Show what exists and ask which to execute. - If no plans exist, tell the user to run
/planfirst.
- Detect format (see Format Detection below)
- Run the Definition of Ready gate (see Definition of Ready below)
- Read all available story documents thoroughly. Understand every step AND every acceptance criterion.
- Identify verification stack: Examine the project to determine what's available:
- Test runner (e.g.
php artisan test,npm test,pytest) - Linter (e.g.
phpstan,eslint,pint,ruff) - Type checker (e.g.
vue-tsc,tsc --noEmit,mypy) - Any custom checks mentioned in the plan
- Record these in the journal header as the verification stack
- Test runner (e.g.
- Set up the git branch (see Git Workflow below)
- Update GitHub ticket status (new format only — see GitHub Integration below)
- Create the journal file alongside the plan
- Write the journal header (including "Documents available" status)
- Begin executing Step 1
Format Detection
Detect whether this is the new multi-file story format or the old monolithic iteration format:
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 606 lines · 109 tokens per session scan A 458e2af70b67
execute is a skill published in the GitHub repository ABilenduke/copilot-developer (4 stars, last pushed 1mo ago), licensed MIT. It adds 109 tokens to every session and 5,737 once invoked, about $0.0004 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
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.