Borrowing it
Nothing to install: this file belongs to alexjbarnes/cockpit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/alexjbarnes/cockpit/main/.claude/skills/accept-issue/SKILL.mdgit clone --depth 1 https://github.com/alexjbarnes/cockpitWrote 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/alexjbarnes/cockpit/accept-issue)<a href="https://agentmods.dev/skills/alexjbarnes/cockpit/accept-issue"><img src="https://agentmods.dev/badge/skills/alexjbarnes/cockpit/accept-issue.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00112 | $0.02597 |
| Opus 5 | $0.00056 | $0.01299 |
| Sonnet 5 | $0.00022 | $0.00519 |
| Haiku 4.5 | $0.00011 | $0.00260 |
Grade A, and why
accept-issue scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **`UNKNOWN`/`BLOCKED`**: GitHub may still be computing mergeability, or a required check/review is missing. Re-query once after a short `curl`-poll; if still not actionable, move to `Code Review` with a comment and sto How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accept and merge a cockpit issue
The final pipeline stage. A human has verified the feature at its live test URL and moved the issue to Accepted. The code already passed CI when the PR was opened and was reviewed inline during implementation. This skill's job is small and should be fast: confirm the PR still merges cleanly with next and that CI is green on the current head, merge it, tear down the ephemeral review surface (test server + worktree), and close the issue out. It also reaps orphaned review surfaces left by rejected issues.
Trust CI; do not re-run the suite locally. GitHub runs typecheck, lint, test, secrets, and socket on the PR in a clean environment. Re-running tsc/build/lint/vitest here only duplicates that, runs against a possibly-stale review worktree, and trips over problems that are pre-existing on next rather than introduced by this issue. The only reason to touch the worktree is to bring the branch up to date with next or to resolve a conflict. After any such push, let CI re-validate the new head; do not verify it yourself.
Input
Either an explicit issue key, or none (the skill selects one).
- An issue key was given (e.g. CK-12): use it (still run the reaper first).
- No key, pipeline mode (a scheduled job): run the reaper, then
mcp__cockpit-config__list_issueswithstatus: "Accepted". If none, stop after reaping. Otherwise pick exactly ONE, oldest byupdatedAt, and process only that. A later run takes the next. - No key, interactive mode (a human ran the skill): run the reaper, then list
Acceptedand ask which to merge.
Step 0: Reap orphaned review surfaces
Run this every invocation, before anything else. It cleans up test servers and worktrees for issues that are no longer under review.
Do this once per repo in scope: list_projects, and for each project's repoPath (falling back to the session's current working directory for a project without one — today's behaviour, and the only case while cockpit is the sole project), call that resolved path <REPO>:
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.
- 7d ago First seen · 86 lines · 112 tokens per session scan A 43f76bfd05e2
accept-issue is a skill published in the GitHub repository alexjbarnes/cockpit (14 stars, last pushed 2d ago), licensed Apache-2.0. It adds 112 tokens to every session and 2,597 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
ln-63-release-publisher
Prepares and publishes an explicitly requested tagged GitHub release. Not for ordinary commits, package publication, or announcements.
ln-64-community-announcer
Drafts or publishes fact-checked GitHub Discussions announcements for project updates. Not for release creation or issue responses.
pr-creator
Creates or updates GitHub PRs with house-style titles and bodies, issue linking, repository templates, and draft state. Use when asked to "create a PR", "rewrite the PR description", or "polish this PR". For code fixes use tidy; for CI and review threads use pr-babysitter; for npm releases use autoship.
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
dev-rc
The last gate before merge — QA, security audit, review and changelog, with objective pass conditions.