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 devoxx/DevoxxGenieIDEAPlugin --skill close-task-commit-push-prgit clone --depth 1 https://github.com/devoxx/DevoxxGenieIDEAPluginWrote 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/devoxx/devoxxgenieideaplugin/close-task-commit-push-pr)<a href="https://agentmods.dev/skills/devoxx/devoxxgenieideaplugin/close-task-commit-push-pr"><img src="https://agentmods.dev/badge/skills/devoxx/devoxxgenieideaplugin/close-task-commit-push-pr/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/devoxx/devoxxgenieideaplugin/close-task-commit-push-pr"><img src="https://agentmods.dev/badge/skills/devoxx/devoxxgenieideaplugin/close-task-commit-push-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 83 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00064 | $0.01046 |
| Opus 5.5 | $0.00026 | $0.00418 |
| Sonnet 5.5 | $0.00013 | $0.00209 |
| Haiku 4.5 | $0.00006 | $0.00105 |
Grade A, and why
close-task-commit-push-pr 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Close Task, Commit, Push & PR
Context
- Current git status: !
git status - Current git diff (staged and unstaged changes): !
git diff HEAD - Current branch: !
git branch --show-current - Main branch: !
git rev-parse --verify main 2>/dev/null && echo main || echo master - Recent commits: !
git log --oneline -10
Your task
Close the active backlog task, commit all changes, push, and open a pull request.
Step 0 — Identify the task
- Extract the task ID from the current branch name (e.g.
feature/task-113-split-css-modules→task-113). - If no task ID is found in the branch name, ask the user which task to close.
Step 1 — Close the backlog task
Close the task before committing so the task file changes are included in the commit and PR.
- Use
mcp__backlog__task_viewto read the task details (title, acceptance criteria). - Use
mcp__backlog__task_editto:- Set status to
Done - Check off all acceptance criteria that were completed (review the diff to determine which ones)
- Write a
finalSummarythat concisely describes what was implemented
- Set status to
- Use
mcp__backlog__task_completeto move the task to the completed folder.
Step 2 — Analyze changes and plan commits
Before committing, analyze git status and git diff HEAD to identify logically distinct groups of changes. Group by feature or concern — for example:
- New files that form a self-contained module → one commit
- Modifications to an existing file that depend on the new module → separate commit
- Task/backlog file changes → include in the final commit (or a dedicated chore commit)
Print a short commit plan (list of planned commits with the files in each) so the grouping is visible.
Step 3 — Commit
- Create one commit per logical group identified above. Stage only the files for that group using explicit file names (never
git add -A; never stage.envor credential files). - Write a clean, descriptive commit message for each commit using conventional commits style.
- End every commit message with:
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]> - Use a HEREDOC to pass the commit message for correct formatting.
- Include the closed task file in the final commit.
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 · 96 lines · 64 tokens per session scan A b091de88af96
close-task-commit-push-pr is a skill published in the GitHub repository devoxx/DevoxxGenieIDEAPlugin (685 stars, last pushed 2d ago), licensed MIT. It adds 64 tokens to every session and 1,046 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-30.
Other skills, from other repositories
dev-finish
Close out a session — summarise what changed, capture what was learned, and prepare the commit.
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
team-release
Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.
release
Use this skill for EVERY ClawRouter release. Enforces the full checklist — version sync, CHANGELOG, build, tests, npm publish, git tag, GitHub release. No step can be skipped.
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.