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 alexmond/alexmskills --skill implement-issuegit clone --depth 1 https://github.com/alexmond/alexmskillsWrote 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/alexmond/alexmskills/implement-issue)<a href="https://agentmods.dev/skills/alexmond/alexmskills/implement-issue"><img src="https://agentmods.dev/badge/skills/alexmond/alexmskills/implement-issue/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/alexmond/alexmskills/implement-issue"><img src="https://agentmods.dev/badge/skills/alexmond/alexmskills/implement-issue.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.00069 | $0.00593 |
| Opus 5.5 | $0.00028 | $0.00237 |
| Sonnet 5.5 | $0.00014 | $0.00119 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
implement-issue 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex: Read the client path before applying this workflow.
Implement GitHub issue #$ARGUMENTS
Try it:
/implement-issue:implement-issue 42— invoke explicitly with the issue number (model auto-invocation is disabled).
Follow this workflow for every code change. It is independent of language and build tool — adapt the build and test commands to whatever the project uses.
Step 1: Read the issue
gh issue view $ARGUMENTS
Understand the requirements before writing any code. If the issue is ambiguous, note your assumptions.
Step 2: Create a feature branch
git checkout main
git pull
git checkout -b feature/$ARGUMENTS-<short-description>
Use a concise, hyphenated <short-description> derived from the issue title.
Step 3: Implement the changes
- Read relevant source files before making modifications.
- Follow the project's existing coding standards and conventions (formatting, language version, libraries already in use).
- Keep changes focused on the issue requirements — avoid unrelated refactors.
Step 4: Build and run tests
Run the project's build and test commands. Discover them from the repo rather than assuming a specific tool — for example a Maven project might use ./mvnw test, but other projects use Gradle, npm, pytest, go test, etc.
Fix any failures before proceeding.
Step 5: Commit and push
git add <changed-files>
git commit -m "<descriptive message>
Closes #$ARGUMENTS
Co-Authored-By: Claude <[email protected]>"
git push -u origin HEAD
Step 6: Create the pull request
gh pr create --title "<concise title>" --body "## Summary
<bullet points of what changed and why>
## Test plan
<how to verify the change>
Closes #$ARGUMENTS
🤖 Generated with [Claude Code](https://claude.com/claude-code)"
Report the PR URL when done.
Git safety
- Never force-push (
git push --force) or delete branches without explicit confirmation from the user. - Push to the feature branch only; do not push directly to
main.
What ships with it
1 file 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 Changed · +3 lines 16056d924824
- 1mo ago First seen · 77 lines · 69 tokens per session scan A edfd1776f2fe
implement-issue is a skill published in the GitHub repository alexmond/alexmskills (9 stars, last pushed 6d ago), licensed MIT. It adds 69 tokens to every session and 593 once invoked, about $0.0003 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
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
team-release
Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.
github-monitor
Watch your GitHub repos across four views - a combined urgency monitor (stale PRs, new issues, releases), a new-issue triage queue, a release upgrade digest, or your own opened-PR tracker.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
start-task
Create a feature branch for a backlog task, switch to it, and start implementation. Use when the user says "start task-123", "work on task-123", "implement task-123", or invokes /start-task with a task ID.