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/p2ergmbh/agentic-coding/github-issue-completenpx skills add P2ERGmbH/agentic-coding --skill github-issue-completegit clone --depth 1 https://github.com/P2ERGmbH/agentic-codingWhat 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.00048 | $0.01740 |
| Opus 5 | $0.00024 | $0.00870 |
| Sonnet 5 | $0.00010 | $0.00348 |
| Haiku 4.5 | $0.00005 | $0.00174 |
Grade A, and why
github-issue-complete 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 2d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Complete Workflow (Full Auto)
This skill provides a "one-stop shop" for the entire software development lifecycle on GitHub. It implements a dual-issue strategy: a Main Issue (human-facing) for project management and a Sub-Issue (agent-facing) for implementation.
📋 Mandatory Task List (task.md)
At the very beginning of Phase 1, the agent MUST initialize and maintain a local task.md file in the workspace containing all steps of the workflow. The agent must update the progress ([ ] to [/] to [x]) continuously and print the updated plan explicitly to the user.
Mandatory task.md Template:
- [ ] Phase 1: Initialization & Strategy
- [ ] Determine/Fetch Main Issue
- [ ] Create/Prepare Human-Facing Main Issue with assignments (read from `package.json` `"agents"` block or fallback `docs/project.json` stakeholders)
- [ ] Create Agent Issue (Sub-Issue, title prefix `[Agent]`) and link natively via helper script or fallback
- [ ] Link Agent Issue inside Main Issue checklist
- [ ] Phase 2: Implementation & Validation
- [ ] Set up Git Worktree and copy `.env` configuration
- [ ] Implement features and refactorings
- [ ] Perform Code Verification (Unit tests, TypeScript compile check, ESLint verification)
- [ ] Perform Local Code Review (utilizing `review-code` skill inside a generalist subagent)
- [ ] Create Pull Request (Title: `feat: ...`, body resolves Agent Issue, references Main Issue)
- [ ] Phase 3: Quality Gate & Review
- [ ] Trigger remote PR review via `review-pull-request` skill
- [ ] Resolve any review findings via `resolve-review` skill
- [ ] Phase 4: Finalization & Handover
- [ ] Update Main Issue checklist to complete
- [ ] Add `test` label to Main Issue
- [ ] Post Browser Click Path and testing instructions comments on Main Issue
- [ ] Ask user to test locally and confirm task completion BEFORE running cleanup
- [ ] Run `npm run log:clear` to clean temporary log files
- [ ] Present final summary with links to Main Issue, Agent Issue, and Pull Request
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.
- 2d ago First seen · 110 lines · 48 tokens per session scan A 23b4db746fd2
github-issue-complete is a skill published in the GitHub repository P2ERGmbH/agentic-coding (9 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 1,740 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…